Abstract: A network routing server can be configured to receive client requests from multiple client devices and route the client requests to optimal service providers to service the request. To determine which service provider is optimal to service the client request, the network routing service can analyze multiple factors, such as geographic location of the client, geographic location of the service providers, and health metrics describing service quality of the various service providers. Health metrics can include Central Processing Unit (CPU) usage, bandwidth, memory usage, connectivity, service providers network status, network latency, user capacity saturation, etc. Based on an analysis of this data, the network routing service can determine the service provider that is best suited to service the client request and route the client request accordingly.

Abstract: A single global traffic optimizer can be configured to perform the functionality of a global and local traffic manager. For example, the global traffic optimizer can receive a client request from a client device and route the client request to an appropriate service provider from a set of geographically dispersed service providers to service the client request. In addition to the geographic location data of the client device and service providers, the global traffic optimizer can also analyze health metrics describing service quality of the various service providers, such as Central Processing Unit (CPU) usage, bandwidth, memory usage, connectivity, service provider's network status, network latency, user capacity saturation, etc. Based on an analysis of this data, the global traffic optimizer can determine the service provider that is best suited to service the client request and route the client request accordingly without need for a local traffic manager.

Abstract: A single DNS NS record can establish a zone delegation to a reverse proxy access device so that the reverse proxy access device answers DNS queries directed to it under the zone delegation. A DNS label can be designated at the reverse proxy access device for each resource served by the reverse proxy access device. Upon receiving a DNS request directed to the reverse proxy access device under the zone delegation, the reverse proxy access device can use the DNS label included in a DNS request to identify the specific resource and answer with an automatically and dynamically generated A record containing the IP address of the reverse proxy access device. The client can then use the IP address to complete a TCP connection with the reverse proxy access device, after which the reverse proxy access device can use the DNS label to complete the request to the appropriate resource.