Your CDN saved you from explaining a 400ms load time to your VP.
Then your deploy shipped. And nobody got the fix.
Here's what happened:
Your edge nodes were still serving the old JS bundle — TTL hadn't expired. You triggered a cache purge manually. But you hit the wrong environment. Prod kept serving the stale version for 6 more hours.
You need a CDN configuration that handles invalidation reliably under deploy pressure. Which one do you pick?
A) Anycast routing + stale-while-revalidate + event-driven purge via API on deploy
B) Unicast routing + aggressive TTLs + manual cache purge via dashboard
C) Anycast routing + long TTLs + tag-based invalidation via API
D) Anycast routing + short TTLs + no invalidation strategy (let caches expire naturally)
Pick A, B, C, or D — and tell me what your actual CDN invalidation story is. Full breakdown in the comments.
