Why our cache kept serving stale data
Problem
Users saw old prices for minutes after an update, even though the cache TTL was only 30 seconds.
What we learned
A second cache layer in the CDN was ignoring our headers and holding responses for 10 minutes.
Takeaways
- Map every cache layer before tuning one
- Invalidate on write, don't rely on TTL alone
Related
Cache invalidation patterns · Debugging with an Agent