On the 4th day of Windows Azure Platform Christmas my true love gave to me the Content Delivery Network.
What is the Content Delivery Network?
The Windows Azure Content Delivery Network (CDN) caches Windows Azure Blobs (discussed on day two), at locations closer to where the content is being requested, this way bandwidth is maximised and content is delivered faster.
For example, say you have a website that delivers video content to millions of users around the world, that’s a lot of locations It would be terribly inefficient to serve up content from just one location. Allowing the video content to be cached in several locations, some being closer to the requesting source allows for the video to streamed/downloaded quicker.
There’s only one requirement to make a blob (your data) available to the CDN and it’s very simple, mark the container the blob resides in as public. To do this, you need to enable CDN access to your Storage Account.
Enabling CDN access to a Storage Account is done through the Management Portal (briefly mentioned on day two). When CDN access has been enabled the portal will provide you with a CDN domain name in the following URL format: http://<identifier>.vo.msecnd.net/.
NOTE: It takes around 60 minutes for the registration of the domain name to propagate round the CDN.
With a CDN domain name and a public container with blobs in, you now have the ability to serve up Windows Azure hosted content; strategically, to the world
Tomorrow’s installment: Connect
P.S. If you have any questions, corrections or suggestions to make please let me know.