The myth that origin shield is overkill

The myth that origin shield is overkill
A Cape Town media site skipped origin shield, told it was an enterprise luxury they didn't need. Then a homepage feature went viral and their origin took 8,000 simultaneous cache-miss requests for the same uncached video poster.
The myth: a shield is unnecessary complexity. The reality: without it, every edge PoP independently fetches a cold object from origin. One viral miss became thousands of identical origin hits, the thundering herd.
What we changed: we enabled origin shield in a single region, so all PoPs fetch through one collapsing layer. Identical requests dedupe into one origin call.
Result: during the next spike, origin saw 12 requests instead of 8,000, and CPU stayed under 20%.
A shield is request coalescing, not a luxury. It saves you on the day traffic spikes.
The number that mattered: 12 origin requests instead of 8,000.