Skip to content

Content Delivery Network

A CDN distributes web content across locations. Public files can be cached there; personalised portal responses need their own cache rules.

Also known asCDN
Cloud & Operations

What is a Content Delivery Network?

A Content Delivery Network (CDN) serves web content through distributed servers. MDN explains keeping copies at multiple locations. On a suitable cache hit, a stored copy can answer the request. A missing copy must first be obtained from the origin server. The effect therefore depends on content, configuration and actual requests.

Example: distributing a public manual

In the fictional example, the freely accessible manual handbuch-v1.pdf is delivered through a CDN. For the new edition, the team publishes handbuch-v2.pdf and updates the website links. It checks which edition arrives through each address. Replacing a file at an unchanged address would also require an appropriate update or removal of cached copies.

In this design, personalised project reports from the portal must stay out of the shared CDN cache. MDN distinguishes private from shared caches and warns about sharing personalised content. The team must align response headers with the CDN rules actually in effect; a login alone is insufficient evidence.

A CDN replaces neither the application’s access checks nor a backup and recovery plan. Whether it improves delivery should be measured for the required files and user locations.

Sources

Articles on this topic

Cloud & Operations with ASES

Hosting, deployment, maintenance and support