Microsoft Technology Licensing, LLC

Pradeepkumar Mani

Jie Jerry Liu

David A Maltz

Ashley Flavel

Nick Holt

Oleg Surmachev

Lihua Yuan

Ashok Kumar Nandoori

Abhishek Agarwal

Nalin Raj Gupta

Rami Y Al-dalky

Pranav Agarwal

Jie Liu

A system for load management in a shared address networking architecture includes a primary point-of-presence (POP) group of servers configured to serve content of a domain and that are each reachable at an address of a first IP address block and a secondary PoP group of servers configured to serve the content of the domain and that are each reachable at an address of a second IP address block. The system further includes a traffic management agent configured to reduce a total volume of incoming requests received by the primary PoP group for a period of time following a return of a first server in the primary PoP group of servers to an online state by selectively directing a first percentage of the incoming requests to the second IP address block instead of the first IP address block.

Load management for servers in shared address network architecture

Techniques are described for securely managing computing resources in a computing environment comprising a computing service provider and a remote computing network. The remote computing network includes computing and network devices configured to extend computing resources of the computing service provider to remote users of the computing service provider. The network devices include a trusted network device that includes a root of trust. The trusted network device detects that a new device is communicatively coupled to a port on the trusted network device. The trusted network device determines that the new device is not authorized to access computing resources at the remote computing network. The port is isolated at the trusted network device.

Securing network access at edge sites using trusted network devices

N nodes are assigned to a first layer of nodes having a first domain name server (DNS) anycast Internet Protocol (IP) address and a first fully qualified domain name (FQDN). M nodes are assigned to a second layer of nodes having a second DNS anycast IP address and a second FQDN. When a request to resolve the first FQDN for the first layer of nodes is received by a DNS of a node of the first layer and a load on the ES of the node is less than a threshold, the DNS handles the request by returning an edge server (ES) anycast IP address for the ES of the node. When the load on the ES is greater than the threshold, the DNS offloads the request by returning the second FQDN so that the second FQDN of the second layer is resolved to the second DNS anycast IP address.

Load balancing with layered edge servers

A Top of Rack (TOR) switch operating with a Software for Open Networking in the Cloud (SONiC) platform is implemented using commodity switch hardware and is configured to maintain or retrieve flow state information for incoming data flows in a load balancer. In one embodiment, an application-specific integrated circuit (ASIC) informs a user mode container flow state information for each incoming data flow. The user mode container informs the ASIC of any affected flows that may result pursuant to a modified distributed system (e.g., added, updated, or removed servers). In other embodiments, the ASIC may utilize remote direct memory access (RDMA) to retrieve flow state information maintained by a remote device or may utilize the RDMA to retrieve network address translation (NAT) information for incoming traffic. In each of the implementations, the integrity of the load balancing system is maintained when the distributed system of servers changes.

Hardware load balancer gateway on commodity switch hardware

An edge server node comprises an edge server, a DNS, and a load controller. The DNS is assigned to a layer of edge server nodes where each layer of edge server nodes has a DNS anycast IP address for the DNSs of that layer and a FQDN for that layer. The DNS either handles or offloads requests to resolve the FQDN for the assigned layer to balance the load on the edge server. A request is offloaded by returning the FQDN for another layer. The load controller monitors the load on the edge server and directs the DNS to offload requests to reduce the load on the edge server.

Growing community of inventors

Issaquah, WA, United States of America

Pradeepkumar Mani