Dynamic binding and load determination in a content delivery network
A content provider has a plurality of content provider domain names, and a content delivery network (CDN) allocates a plurality of CDN domain names to the particular content provider. The content provider domain names are mapped to the CDN domain names. CDN domain names are bound to corresponding CDN clusters. The binding of the of CDN domain names to corresponding CDN clusters is modified.
1 . A computer-implemented method, in a network, wherein said network delivers data on behalf of a data provider, and wherein the data provider has a first plurality of provider domain names associated therewith, and wherein said network allocates a first plurality of network domain names to said data provider, and wherein said first plurality of provider domain names are mapped to said first plurality of network domain names, wherein said network comprises a plurality of clusters, the method comprising:
(A) maintaining a binding of said first plurality of network domain names to corresponding clusters, wherein each of said first plurality of network domain names is bound to at least one cluster;
(B) maintaining, for at least some of said clusters, a first mapping; and then
(C) determining a second mapping, based on at least correlating the first plurality of provider domain names included in one or more data requests received at one or more clusters with the one or more clusters receiving such requests and using the first mapping to correlate the first plurality of provider domain names to the first plurality of network domain names; and
(D) determining an amount of traffic or load associated with a particular domain name of said data provider; and
(E) based at least in part on said amount of traffic or load determined in (D) and the second mapping, modifying said binding of said first plurality of network domain names to corresponding clusters.
2 . The method of claim 1 , wherein said plurality of provider domain names are mapped in a many-to-one relationship to a plurality of network hostnames.
3 . The method of claim 1 , wherein said plurality of provider domain names are mapped using canonical names (CNAMEs) to said plurality of network domain names.
4 . The method of claim 1 , wherein each of said first plurality of network domain names has a corresponding unique identifier associated therewith.
5 . The method of claim 4 , wherein a set of cluster/VIP pairs associated with each network domain name is determined based on a hash function applied to the unique identifier associated with that network domain name.
6 . The method of claim 1 , wherein a set of cluster/VIP pairs associated with each network domain name is unique for each network domain name.
7 . The method of claim 1 , wherein each network domain name has a unique VIP at each of a plurality of clusters.
8 . The method of claim 1 , wherein the binding of said first plurality of network domain names to corresponding clusters is maintained in a rendezvous system of said network.
9 . The method of claim 1 , wherein, for said determining in (C), the one or more requests comprise one or more requests for data of said data provider.
10 . The method of claim 1 , wherein said modifying in (E) increases the number of clusters associated with a particular network domain name.
11 . The method of claim 1 , wherein said modifying in (E) decreases the number of clusters associated with a particular network domain name.
12 . The method of claim 1 , wherein at least one of said clusters comprises multiple marker clusters.
13 . A nontransitory article of manufacture comprising a computer-readable medium having program instructions stored thereon, the program instructions, operable on a computer system in a network,
wherein said network delivers data on behalf of a data provider, and
wherein the data provider has a first plurality of provider domain names associated therewith, and wherein said network allocates a first plurality of network domain names to said data provider, and wherein said first plurality of provider domain names are mapped to said first plurality of network domain names, wherein said network comprises a plurality of clusters,
wherein execution of the program instructions by one or more processors of said computer system causes the one or more processors to carry out the acts of:
(A) maintaining a binding of said first plurality of network domain names to corresponding clusters, wherein each of said first plurality of network domain names is bound to at least one cluster;
(B) maintaining, for at least some of said clusters, a first mapping; and then
(C) determining a second mapping, based on at least correlating the first plurality of provider domain names included in one or more data requests received at one or more clusters with the one or more clusters receiving such requests and using the first mapping to correlate the first plurality of provider domain names to the first plurality of network domain names; and
(D) determining an amount of traffic or load associated with a particular domain name of said data provider; and
(E) based at least in part on said amount of traffic or load determined in (D) and the second mapping, modifying said binding of said first plurality of network domain names to corresponding clusters.
14 . The nontransitory article of manufacture of claim 13 , wherein said plurality of content provider domain names are mapped in a many-to-one relationship to a plurality of network hostnames.
15 . The nontransitory article of manufacture of claim 13 , wherein said plurality of provider domain names are mapped using canonical names (CNAMEs) to said plurality of network domain names.
16 . The nontransitory article of manufacture of claim 13 , wherein each of said first plurality of network domain names has a corresponding unique identifier associated therewith.
17 . The nontransitory article of manufacture of claim 16 , wherein a set of cluster/VIP pairs associated with each network domain name is determined based on a hash function applied to the unique identifier associated with that network domain name.
18 . The nontransitory article of manufacture of claim 13 , wherein a set of cluster/VIP pairs associated with each network domain name is unique for each network domain name.
19 . The nontransitory article of manufacture of claim 13 , wherein each network domain name has a unique VIP at each of a plurality of clusters.
20 . The nontransitory article of manufacture of claim 13 , wherein the binding of said first plurality of network domain names to corresponding clusters is maintained in a rendezvous system of said network.
21 . The nontransitory article of manufacture of claim 13 , wherein, for said determining in (C), the one or more requests comprise one or more requests for data of said data provider.
22 . The nontransitory article of manufacture of claim 13 , wherein at least one of said clusters comprises multiple marker clusters.
23 . A device in a network, wherein said network delivers data on behalf of a data provider, wherein the data provider has a first plurality of provider domain names associated therewith, wherein said network allocates a first plurality of network domain names to said data provider, wherein said first plurality of provider domain names are mapped to said first plurality of network domain names, wherein said network comprises a plurality of clusters, and wherein the device comprises:
at least one processor; and
memory, operatively connected to the at least one processor storing instructions that, when executed by the at least one processor, cause the device to:
(a) maintain a binding of said first plurality of network domain names to corresponding clusters, wherein each of said first plurality of network domain names is bound to at least one cluster;
(b) maintain, for at least some of said clusters, a first mapping; and then
(c) determine a second mapping, based on at least correlating the first plurality of provider domain names included in one or more data requests received at one or more clusters with the one or more clusters receiving such requests and using the first mapping to correlate the first plurality of provider domain names to the first plurality of network domain names; and
(d) determine an amount of traffic or load associated with a particular domain name of said data provider; and
(e) based at least in part on said amount of traffic or load determined in (d) and the second mapping, modify said binding of said first plurality of network domain names to corresponding clusters.
24 . The device of claim 23 , wherein said plurality of provider domain names are mapped in a many-to-one relationship to said plurality of network hostnames.