Azure Content Delivery Network (CDN) can be defined as a distributed network of servers that can efficiently deliver content to end users. CDNs also store cached content on edge servers at point-of-presence locations close to end users to minimize latency. CDNs provide developers with a global, high-bandwidth content platform for their users by caching their content in strategically placed physical nodes around the world.
Benefits of the Azure Content Delivery Network are:
User requests are distributed and handled directly by edge servers, resulting in less traffic sent to the origin or main servers.
Larger scale to better handle sudden high loads.
Improved end-user performance and user experience.
Limitations:
The limitations are as follows:
The number of custom domains that can be mapped to endpoints.
Number of profiles that can be created.
The number of endpoints that can be created in endpoints.
How it works:
A user (Steve) requests a file (also called an asset) by using a URL with a special domain name, such as <endpoint name>.azureedge.net. This name can be an endpoint hostname or a custom domain. The DNS routes the request to the best performing POP location, which is usually the POP that is geographically closest to the user.
If no edge servers in the POP have the file in their cache, the POP requests the file from the origin server. The origin server can be an Azure Web App, Azure Cloud Service, Azure Storage account, or any publicly accessible web server.
The origin server returns the file to an edge server in the POP.
An edge server in the POP caches the file and returns the file to the original requestor (Steve). The file remains cached on the edge server in the POP until the time-to-live (TTL) specified by its HTTP headers expires. If the origin server didn't specify a TTL, the default TTL is seven days.
Additional users can then request the same file by using the same URL that Steve used and can also be directed to the same POP.
If the TTL for the file hasn't expired, the POP edge server returns the file directly from the cache. This process results in a faster, more responsive user experience.
Comentarios