build1 publisher
Invalidating a cache tag on one Next.js instance leaves the other one serving sold-out stock
A dev.to postmortem traces a 2 AM rollback to per-instance caches and rebuild timers, and the part of the fix that actually crosses instances is a cacheHandler writing invalidation timestamps to shared storage.
Publishers:dev.to
Reality
- Evidence32
- Adoption10
- Hype gap+30
- Incentives45
- Confidence35