What it is and the problem it solves
A CDN is a geographically distributed network of proxy servers and data centres. It solves the problem of distance-induced latency and origin-server overload by serving cached content from locations nearer to users.
How it works
CDNs route requests algorithmically to geographically distributed nodes — proxy servers and data centres — that cache content closer to users. Nodes sit over multiple Internet backbones. Origin servers remain the source of truth; edge servers serve cached copies.
What works
CDNs reliably serve a large portion of internet content — text, graphics, scripts, downloadable objects, applications, live and on-demand streaming media, and social media services. Their algorithmic routing, caching, and load balancing deliver measurable improvements in availability and performance.
What does not
CDNs do not eliminate latency entirely. They do not guarantee privacy compliance under GDPR without additional technical responses like Subresource Integrity or edns-client-subnet. They do not override the end-to-end principle — they operate within it, not against it.
What it changes
CDNs change where content lives in the network. They shift delivery from central origins to dispersed edges. This alters economic flows (content providers pay CDN operators who pay ISPs) and introduces new failure modes — caching stale content, misrouted requests, or inconsistent security enforcement across PoPs.
Is it worth your time
Yes, if you deliver web content at scale. CDNs reduce bandwidth costs, improve page load times, and increase global availability. They are a foundational layer in the internet ecosystem — not optional infrastructure, but embedded infrastructure.
