←  All terms
C
Hosting & Infrastructure

CDN

A content delivery network distributes content across regional servers to reduce latency, loading time, and origin-server load.

A content delivery network distributes content across regional servers to reduce latency, loading time, and origin-server load. A robust setup considers availability, security, scalability, observability, and a tested recovery path. The concept is closely related to Caching and Edge Computing.

Read more

Caching

Edge Computing

Time to First Byte

Hosting

FAQ

CDN

What typical mistakes occur when using a CDN?
Typical mistakes are wrong cache rules that serve outdated pages, caching personalized responses, and missing invalidation after deployments. Data processing outside the EU is also overlooked when locations are not reviewed. Rules, locations, and the contractual basis should be clarified before rollout.
Can a CDN improve the resilience and security of a website?
Partly. A CDN absorbs traffic peaks and can serve content during short origin outages if it sits in the cache. Many providers also offer protection against attacks. Dynamic content and the origin server remain a weak point that needs its own safeguards and monitoring.
How do a CDN and caching differ?
Caching is the principle of keeping copies at hand, while a CDN is an infrastructure that operates caching at many locations near users. A CDN uses caching but does not replace cache control through headers and rules. The two must be aligned so that changes become visible promptly.
When is a CDN worthwhile for a website?
A CDN pays off with visitors in several regions, high traffic peaks, or many static files. It lowers latency and relieves the origin server. With a purely local audience and low traffic the effect is smaller, but so is the extra effort, since many hosting offerings already include a CDN.