Friday, 2 September 2016

Microsoft Azure Content Delivery Networks Aka CDN

In our couple of blog post related to Azure we discussed about Understanding Microsoft AzureVirtual Networks ,Azure ManagementTools , Azure Virtual Machines ,Demystified Azure Websites , Securing Azure Virtual Machines and also talked about Azure Paas Cloud Services, dedicated this article to understand the Content Delivery Networks Aka CDN.

How cool it's gonna be when we can access the content including files, videos,images with Speed irrespective of the fact wherever we are in the world? Sound Like a Plan isn't it.

Well this is what Microsoft Azure Content Delivery Network does by delivering the content as close as possible to end users no matter wherever they are in the World.


When the user request for the content the request is forwarded to CDN server which is close to user's location, we can create our own CDN by configuring the Azure Content Delivery Network service which can cache content from Azure storage accounts, PaaS cloud services, virtual machines in IaaS cloud services, or Azure websites.

Content Delivery Networks provides various advantage to end users in terms of the overall User Experience when they are situated at a long distance from the content. 

The content's which are part of Azure CDN also provides us the protection against Denial of Service Attack not only because it includes systems to detect and mitigate the risks but also because of the fact that the content are being replicated in many locations.

One of the prerequisites before we create Azure CDN is that we need to take care of is the Azure Storage which is required initially and later Azure CDN capabilities can be added but that doesn't mean that both the Azure CDN and Storage are billed together :-).

As soon as CDN is created it is going to create multiple Endpoints which are Distributed Globally to ensure the End users can access the data which is Geographically near to them irrespective of the fact wherever they are.

If the user is trying to access the data it would be retrieved from the nearest endpoint based on his geographical location but if in case the data is not available in the nearest location it would be retrieved from Azure Storage and cached at the endpoint.
  

No comments:

Post a comment