Origin shield vs. plain tiered cache: a Frankfurt media site picks wrong

Origin shield vs. plain tiered cache: a Frankfurt media site picks wrong
A news site serving 12M monthly views ran a standard CDN with 200+ edge PoPs hitting origin directly. Every cache miss in Mumbai, São Paulo, and Lagos stampeded the same origin in Frankfurt at once.
Origin egress hit 4.2 TB/day and the box maxed CPU at every publish.
They enabled origin shield — a single designated PoP that absorbs all misses, so origin sees one request instead of forty. Tiered cache alone would have helped, but the shield collapsed the fan-in to a chosen low-latency PoP.
Origin requests dropped 71%. Egress fell to 1.3 TB/day. Frankfurt CPU settled at 40%.
Use a shield when origin is far from most edges and content is hot. Skip it when content is hyper-personalized — the shield just caches nothing.
The number that mattered: 71% fewer origin hits.