The purpose of a content delivery system or CDN is to distribute content to multiple nodes so that it becomes more easily accessible. Rather than distributing content from central location where it would always travel across large parts of the network it is stored at nodes that are closer to the peripheries. It can then be accessed from the closest point or in the case of spikes in demand it can be accessed from multiple locations.
CDN hosting is supplied by an application service provider (ASP) and can make use of existing infrastructure that is paid for as it is used. Telcom providers have also been introducing content delivery networks on their own infrastructure. There are also some providers that rely on peer-to-peer networks
There will always be a backbone networks that connects all the nodes which might consist of thousands of edge servers. Except in the case of peer-to-peer there will also be central servers where backup information is stored. Content is stored on the central servers which are closest to the nodes that are used most often. From here it will be sent to many different nodes where it can be accessed as needed.
The application software will route request for content to the server which is closest or which has higher availability. This means that less of the overall network is used which reduces the overall load on it. Downloads will be quicker and more stable but there will also be a lower costs if the network is paid for as it is used. The software also decides how the information is moved around as demands change.
When you need to deliver content that requires high bandwidth capability this is the ideal solution and it is used by online broadcasting and video download services. One of the big advantages is scalability. If there is very high demand the content can be accessed from multiple nodes and so the system won't crash.
The effective broadband capacity is also increased with every added node. If the backbone network has a capacity of 10Gbit/s then that would be the limit for transfer across the system. If each separate node could be accessed at 10Gbit/s then that could be multiplied for every node that is available. Say there where 100 nodes with the same content on then it would be possible to transfer at 1Tbit/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 hosting is supplied by an application service provider (ASP) and can make use of existing infrastructure that is paid for as it is used. Telcom providers have also been introducing content delivery networks on their own infrastructure. There are also some providers that rely on peer-to-peer networks
There will always be a backbone networks that connects all the nodes which might consist of thousands of edge servers. Except in the case of peer-to-peer there will also be central servers where backup information is stored. Content is stored on the central servers which are closest to the nodes that are used most often. From here it will be sent to many different nodes where it can be accessed as needed.
The application software will route request for content to the server which is closest or which has higher availability. This means that less of the overall network is used which reduces the overall load on it. Downloads will be quicker and more stable but there will also be a lower costs if the network is paid for as it is used. The software also decides how the information is moved around as demands change.
When you need to deliver content that requires high bandwidth capability this is the ideal solution and it is used by online broadcasting and video download services. One of the big advantages is scalability. If there is very high demand the content can be accessed from multiple nodes and so the system won't crash.
The effective broadband capacity is also increased with every added node. If the backbone network has a capacity of 10Gbit/s then that would be the limit for transfer across the system. If each separate node could be accessed at 10Gbit/s then that could be multiplied for every node that is available. Say there where 100 nodes with the same content on then it would be possible to transfer at 1Tbit/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 UK CDN makes it possible for big amounts of data to be shared. Visit Vi.net for the best in CDN solutions
No comments:
Post a Comment