Just read this article about Static website hosting in Azure Storage :
For the moment, I use to deploy my static content to Azure CDN.
So far here are the difference that I've found:
I am wondering what could be a good candidate for Static website hosting in Azure Storage:
Content for local application that does not need to scale globally ?
As the official said, the benefits of using Azure CDN to deliver web site assets include:
Better performance and improved user experience for end users, especially when using applications in which multiple round-trips are required to load content.
Large scaling to better handle instantaneous high loads, such as the start of a product launch event.
Distribution of user requests and serving of content directly from edge servers so that less traffic is sent to the origin server.
I don't think that host Static website in Azure Storage is a good candidate because of the performance. Below points show the features of CDN which are what Azure Storage do not have:
CDN is a content distribution network built on the network. It relies on the edge servers deployed everywhere, through the load balancing, content distribution, scheduling and other functional modules of the central platform, so that users can get the required content near the network, reduce network congestion, improve the user's access response speed and hit rate. The key technologies of CDN include content storage and distribution technology.
The basic principle of CDN is that various caching servers are widely used to distribute the caching servers to areas or networks which are relatively centralized by users. When users access the web site, the user's access is directed to the nearest working normal cache server using the global load technology, and the cache server is used directly. The household request.
Content distribution network (CDN) is a new network construction method, which is specially optimized for the distribution of broadband media in traditional IP networks, and from a broad sense, CDN represents a network service model based on quality and order.
Simply speaking, content distribution network (CDN) is a strategic deployment of the overall system, including distributed storage, load balancing, network request redirection and content management 4 elements, and content management and the global network traffic management (Traffic Management) is the core of the CDN. Through the judgement of user proximity and server load, CDN ensures that the content provides services for users' requests in a highly efficient way.
In general, content services are based on caching servers, also known as proxy caches (Surrogate), which are located on the edge of the network and are only "one hop" (Single Hop) away from the user. At the same time, proxy caching is a transparent image of the content provider source server (usually located in the data center of the CDN service provider). Such an architecture allows CDN service providers to represent their customers, the content providers, to provide the best possible experience to the end users, which can not tolerate any delay in the response time of the request.
More information about CDN, we can refer to: Content Delivery Network and its Business Benefits
In addition, custom DNS is not only for CDN: Setting up Custom DNS Records to point to Azure Web Sites - with Stefan Schackow
