A CDN for hundreds of domains
A multi-tenant CDN serving hundreds of domains and 50TB of daily traffic, absorbing the load that had been reaching origin servers.
50TB daily traffic sustained
100s of domains served
Hundreds of domains were leaning on their origin servers for traffic a cache should have absorbed, and page load times showed it.
The platform had to sustain 50TB of traffic per day without an operations team dedicated to babysitting it.
I architected and maintained a content delivery network fronting hundreds of domains, tuning caching to keep requests at the edge.
The CDN sustained 50TB of daily traffic, reduced origin hits, and improved page load times across every property.
Architecture
Clients
CDN edge cache + TLS
cache miss
Origins hundreds of domains
// cache hit: the origin never sees the request
Tradeoffs
- — Aggressive caching protects origins but trades content freshness — that tuning is never finished.
- — One shared platform for hundreds of domains buys consistency and concentrates blast radius; changes rolled out carefully.
CDN Edge Caching Performance
Written about Read: Right-Size Your Cloud Infrastructure → Read: Advanced API Gateway Patterns for Microservices →
Want something like this built, or want to talk about the work?