A content delivery system or content delivery network (CDN) makes it possible for large amounts of data to be transferred more efficiently. To do this it distributes copies of the content across the network so that it can be accessed from multiple points. Requests for this information can then be routed to the nearest point or the one that has the least traffic.
CDN networks operate as an application service provider (ASP). The infrastructure that is used can then be outsourced and can be changed as needed. Some internet service providers make use of their own systems for content delivery. This gives then the advantage that they do not have to pay a secondary provider for the infrastructure. Some networks also use peer-to-peer systems that do not require centralized servers.
A CDN is comprised of a network backbone that connects many different nodes or edge servers, redundant central servers and fallback servers. There could be thousands of different nodes and these are distributed so that they are as physically close to the end user as possible. Content is then duplicated on to many different edge servers so that it can be accessed from many different points.
When there is a request for content the system will direct that request to the node which is most suitable. This would be either because it is the closest or because it is the closest server which is not at high capacity. You therefore get the fastest possible connection using the least amount of network resources. In some cases the data can also be routed to take advantage of the least expensive links.
The ideal usage is for high volume content that requires a lot of bandwidth like music and video downloads or online broadcasting but any kind of website can make use of a CDN. When there is a big demand for certain content it can be accessed from many different locations which increases reliability and quality of service. The effective bandwidth of the entire system is also increased.
If the data were to be accessed from a central point then bandwidth would be limited to what the backbone network could carry. By placing this information on many different nodes near the end user the bandwidth is effectively multiplied for every added node. If there are 10 nodes which each carry 10Gbit/s then it would be possible to download 100Gbit/s.
Any kind of content can be distributed by a CDN and this includes static or dynamic websites. If there are any changes to the website of the host server then you will end up with many copies that are cached on the network that would be out of date. By using ESI (edge side includes) these can now be instantly updated when changes occur.
CDN also has other similarities to cloud networking apart from scalability. There is also a high level of redundancy and all your online information is effectively backed up multiple times. This might negate the need for additional online backup. If any part of the content delivery network were to go down request could be redirected to other parts of it so there would be high website availability.
CDN networks operate as an application service provider (ASP). The infrastructure that is used can then be outsourced and can be changed as needed. Some internet service providers make use of their own systems for content delivery. This gives then the advantage that they do not have to pay a secondary provider for the infrastructure. Some networks also use peer-to-peer systems that do not require centralized servers.
A CDN is comprised of a network backbone that connects many different nodes or edge servers, redundant central servers and fallback servers. There could be thousands of different nodes and these are distributed so that they are as physically close to the end user as possible. Content is then duplicated on to many different edge servers so that it can be accessed from many different points.
When there is a request for content the system will direct that request to the node which is most suitable. This would be either because it is the closest or because it is the closest server which is not at high capacity. You therefore get the fastest possible connection using the least amount of network resources. In some cases the data can also be routed to take advantage of the least expensive links.
The ideal usage is for high volume content that requires a lot of bandwidth like music and video downloads or online broadcasting but any kind of website can make use of a CDN. When there is a big demand for certain content it can be accessed from many different locations which increases reliability and quality of service. The effective bandwidth of the entire system is also increased.
If the data were to be accessed from a central point then bandwidth would be limited to what the backbone network could carry. By placing this information on many different nodes near the end user the bandwidth is effectively multiplied for every added node. If there are 10 nodes which each carry 10Gbit/s then it would be possible to download 100Gbit/s.
Any kind of content can be distributed by a CDN and this includes static or dynamic websites. If there are any changes to the website of the host server then you will end up with many copies that are cached on the network that would be out of date. By using ESI (edge side includes) these can now be instantly updated when changes occur.
CDN also has other similarities to cloud networking apart from scalability. There is also a high level of redundancy and all your online information is effectively backed up multiple times. This might negate the need for additional online backup. If any part of the content delivery network were to go down request could be redirected to other parts of it so there would be high website availability.
About the Author:
A content delivery network makes it possible for large quantities of data to be shared. Visit Vi.net for the best in CDN networks
No comments:
Post a Comment