Content delivery for web application hosting is usually involves third party services keeping copies of your application data close to the end-user which offers increased performance, scaling and cost efficiency.
Traditional CDN allows you to store static web assets on a third party server, those assets are then duplicated across the CDN provider’s global network of servers. User requests for dynamic content still hit your web application first, but static content is referenced to the CDN and is delivered from a node local to the end-user.
Advanced or modern CDN is typically coupled with the proxying of traffic, with the proxy being configured to cache and deliver the static parts of your web application and the CDN proxy communicates with your web application on behalf of the user for the dynamic content.
Streaming CDN for live or near-live audio and video are particularly focused on the real-time duplication and re-broadcasting of streaming media and often sourced separately to static CDN.
The choice of CDN is dependent on the type of content to be delivered, the concurrency and quality of streaming or overall volume of data required and reach required. While most CDN have excellent global reach, for countries such as China region specific CDN may be considered.
Last saved: 2021/08/18 at 14:02 by Carl Heaton