Everyone wants a good experience accessing a websites content from any where at any time. Whether we like it or not location comes into play, if I’m trying to stream content from Australia and I’m located in the United Kingdom, you can expect to receive circa 250ms latency, which means a poor user experience.
Microsoft have the answer which is Content Delivery Networks (CDN). Essentially this is a global caching solutions that delivers the website content from a point of presence closest to the users.
Caching Content
When CDN is enabled you will create an endpoint. An endpoint is the URL used to access your cached resources for example http://endpoint.azureedge.net. Each CDN supports up to ten endpoints, which holds one of three types of cached content.
Blob Storage – If your Blob Storage is publicly available then it can be made accessible via CDN
App Services – If you are running App Services then you can again make these available via CDN
Cloud Services – If you are running Cloud Services then you can again make these available via CDN
What Locations Are Used
CDN has a point of presence (POP) in the following locations.
| Australia | Asia | Europe | North America | South America |
| Melbourne
Sydney |
Batam
Hong Kong Jakarta Kaohsiung Osaka Seoul Singapore Tokyo Bangalore Chennai Delhi Mumbai |
Amsterdam
Copenhagen Frankfurt Helsinki London Madrid Milan Paris Stockholm Vienna Warsaw |
Atlanta
Chicago Dallas Philadelphia Los Angeles Miami New York San Jose Seattle Washington DC Boston |
São Paulo
Quito
|
This is shown in the conceptual diagram below.
VMFocus 
2 thoughts on “Microsoft Azure Concepts – Content Delivery Network”