See how edge caching changes latency, origin load, and regional fan-out.
What problem are we solving?
Move traffic closer to users instead of forcing every request through one origin.
Live simulation
updates every 1s
Users 10,000
→
Edge POPs 3 regions
→
Origin 1500/s
85% edge hit
Controls
10000 req/s
85%
140 ms
3
Live metrics
Origin load1,500 req/s
Estimated user latency78 ms
Edge-served8,500 req/s
What just happened?
Raising the hit rate keeps more requests at the edge, so the origin sees less traffic. A CDN is not just a speed trick: it also reduces origin saturation and absorbs traffic bursts.
Try this
Black Friday
Push traffic to 80,000 req/s, then lower the edge hit rate to 50%. Watch the origin load explode.
What would you protect next if the origin still became the bottleneck?
Key takeaway
Cache close to users first when content is repeatable. Then design the origin for the misses that remain.
