Request routing based on class

• US 9,571,389 B2
• Filed: 04/28/2014
• Issued: 02/14/2017
• Est. Priority Date: 03/31/2008
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Richardson, David R., Sivasubramanian, Swaminathan, Marshall, Bradley Eugene, Scofield, Christopher L., Pope, Elmore Eugene
• Primary Examiner(s): Jacobs, Lashonda
• Application Number:
  US14/263,824
• Publication Number:
  US 20140237032A1
• Time in Patent Office: 1,023 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/04 Network management architectures or arrangements
• CPC Class Codes: H04L 45/70 Routing based on monitoring results
• CPC Class Codes: H04L 45/72 Routing based on the source address
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A system and method for management and processing of resource requests is provided. A content delivery network service provider receives a DNS query from a client computing device. The DNS query corresponds to a requested resource from the client computing device. The content delivery network service provider associates the client computing device with a cluster of other client computing devices. Based on routing information for the cluster, the content delivery network service provider routes the DNS query. The process can further include monitoring performance data associated with the delivery of the requested resource and updating the routing information for the cluster based on the performance data for use in processing subsequent requests from client computing devices in the cluster.

Claims

1. A computer-implemented method comprising:

as implemented by one or more computing devices of a content delivery network (CDN) service, the one or more computing devices configured with specific executable instructions,

obtaining a Domain Name System (DNS) query from a client computing device at a first DNS server, wherein the DNS query corresponds to a requested resource and wherein the first DNS server corresponds to the CDN service;

determining a class of the client computing device associated with the DNS query; and

monitoring performance associated with delivery of the requested resource;

determining whether an update to routing information for the class is needed based on the delivery performance; and

if so, modifying the routing information for the class.

2. The method as recited in claim 1, wherein the routing information includes identification of a plurality of cache components, and for individual cache components, information associated with a probability of selection of the individual cache component for delivery of the requested resource.

3. The method as recited in claim 1, wherein the routing information includes a probability of selection of individual DNS servers used for processing the resource request for the determined class.

4. The method as recited in claim 1, wherein determining whether an update to the routing information for the class is needed based on the delivery performance comprises comparing a probability of selection of a first DNS server and other DNS servers.

5. The method as recited in claim 4, wherein modifying the routing information for the class comprises increasing the probability of selection of a DNS server having a lower probability of selection so that the DNS server having a lower probability of selection will be selected more frequently for processing a resource request for the determined class.

6. The method of claim 1 further comprising:

determining whether the first DNS server is authoritative to resolve the DNS query; and

if not, selecting a second DNS server for processing the resource request based on the routing information for the determined class.

7. The method as recited in claim 6, wherein determining whether an update to the routing information for the class is needed based on the delivery performance comprises monitoring performance associated with delivery of the requested resource using the second DNS server.

8. The method as recited in claim 7, wherein modifying the routing information for the class comprises modifying the routing information for the class based on the delivery performance of the requested resource using the second DNS server.

9. The method as recited in claim 8, wherein modifying the routing information for the class comprises modifying a list of DNS servers for processing the resource request for the determined class.

10. The method as recited in claim 8, wherein modifying the routing information for the class comprises modifying probabilities of selection of particular DNS servers used for processing the resource request for the determined class.

11. A system comprising:

a first network point of presence associated with a content delivery network (CDN) service, wherein the first network point of presence includes a Domain Name System (DNS) server that receives a DNS query from a client computing device, wherein the DNS query corresponds to a requested resource, and wherein the DNS server in the first network point of presence is associated with a memory and operative for;

determining a class of the client computing device associated with the DNS query;

monitoring performance associated with delivery of the requested resource;

determining whether an update to routing information for the class is needed based on the delivery performance; and

if so, modifying the routing information for the class.

12. The system as recited in claim 11, wherein the routing information includes identification of a plurality of cache components, and for individual cache components, information associated with a probability of selection of the individual cache component for delivery of the requested resource.

13. The system as recited in claim 11, wherein the routing information includes a probability of selection of individual DNS servers used for processing the resource request for the determined class.

14. The system as recited in claim 11, wherein determining whether an update to the routing information for the class is needed based on the delivery performance comprises comparing a probability of selection of a first DNS server and other DNS servers.

15. The system as recited in claim 14, wherein modifying the routing information for the class comprises increasing the probability of selection of a DNS server having a lower probability of selection so that the DNS server having a lower probability of selection will be selected more frequently for processing a resource request for the determined class.

16. The system of claim 11, wherein the DNS server in the first network point of presence is further operative for:

determining whether the first DNS server is authoritative to resolve the DNS query; and

if not, selecting a second DNS server for processing the resource request based on the routing information for the determined class.

17. The system as recited in claim 16, wherein determining whether an update to the routing information for the class is needed based on the delivery performance comprises monitoring performance associated with delivery of the requested resource using the second DNS server.

18. The system as recited in claim 17, wherein modifying the routing information for the class comprises modifying the routing information for the class based on the delivery performance of the requested resource using the second DNS server.

19. The system as recited in claim 18, wherein modifying the routing information for the class comprises modifying a list of DNS servers for processing the resource request for the determined class.

20. The system as recited in claim 18, wherein modifying the routing information for the class comprises modifying probabilities of selection of particular DNS servers used for processing the resource request for the determined class.

21. A non-transitory, computer-readable storage medium having computer-executable modules for processing a Domain Name System (DNS) query from a client computing device, the DNS query corresponding to a requested resource, the computer-executable modules comprising:

one or more modules configured for;

determining a class of the client computing device associated with the DNS query;

monitoring performance associated with delivery of the requested resource;

determining whether an update to routing information for the class is needed based on the delivery performance; and

if so, modifying the routing information for the class.

22. The non-transitory, computer-readable storage medium as recited in claim 21, wherein the routing information includes identification of a plurality of cache components, and for individual cache components, information associated with a probability of selection of the individual cache component for delivery of the requested resource.

23. The non-transitory, computer-readable storage medium as recited in claim 21, wherein the routing information includes a probability of selection of individual DNS servers used for processing the resource request for the determined class.

24. The non-transitory, computer-readable storage medium as recited in claim 21, wherein determining whether an update to the routing information for the class is needed based on the delivery performance comprises comparing a probability of selection of a first DNS server and other DNS servers.

25. The non-transitory, computer-readable storage medium as recited in claim 24, wherein modifying the routing information for the class comprises increasing the probability of selection of a DNS server having a lower probability of selection so that the DNS server having a lower probability of selection will be selected more frequently for processing a resource request for the determined class.