.png)
A Content Delivery Network (CDN) is a globally distributed cache. It stores copies of your content at edge locations near users, so requests are served locally instead of traveling to a single origin server.
The problems a CDN solves
- Latency: distance = delay; the edge removes it.
- Origin load: cached hits never touch your server.
- Availability: the edge keeps serving even during origin blips.
- Cost: less egress bandwidth from your origin.
Key architectural features
| Feature | What it does | Why it matters |
|---|---|---|
| Edge caching | Stores content at PoPs near users for instant delivery | Eliminates round-trip to origin for cached assets |
| Tiered cache | A regional parent tier shields the origin — more cache hits, fewer origin fetches | Dramatically reduces origin load at scale |
| Smart routing | Routes over the fastest/least-congested path instead of default internet routing | Faster dynamic content even when it can't be cached |
| Cache-control | Headers and TTLs govern what's cached and for how long | Balances freshness vs. performance |
Static vs. dynamic content
Static assets (images, CSS, JS, video) cache beautifully. Dynamic and personalized content benefits from smart routing and connection optimization even when it can't be cached.
Security bonus: because users connect to the CDN edge — not your origin — your origin IP is hidden, shrinking your attack surface. This pairs naturally with a WAF and DDoS protection at the same edge. See our Anycast guide for the underlying routing architecture that makes CDNs fast and resilient.
Contact our engineers to discuss CDN architecture or edge performance for your applications.