🔒 Paid
Cache Eviction Storm
A recent deployment changed what the cache is storing — cached objects got noticeably larger and the number of distinct cache keys in active use has grown substantially. Database read load must stay within its normal operating range: sustained unprotected read pressure against it is treated as a critical incident. Diagnose why eviction rate and hit ratio are moving together in the wrong direction, and bring the cache layer back to a durable, sustainable state rather than one that merely looks stable for now.
- Difficulty
- Senior
- Expected Time
- ~15 min
- Category
- Caching
Skills
- Distinguishing a cache capacity shortfall from a caching-policy/cardinality mismatch
- Recognizing when added memory only delays the same churn at a larger scale
- Protecting a downstream database from cache-miss read pressure
- Evaluating object-shape and admission-policy changes as durable fixes
System Architecture
- API
- Cache
- Database
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents