Design a Redis caching layer with the right patterns, TTLs, key naming, and invalidation to cut latency without serving stale data.
## CONTEXT My application is hitting the database too hard and I want to add a Redis caching layer. I am worried about cache stampedes, stale data, and key sprawl. I want a clear strategy for what to cache, how to name keys, when to invalidate, and how to fail gracefully when Redis is unavailable, all suited to 2026…
Premium Prompt
Unlock this prompt — and all 30,000+ expert-crafted prompts — with Pro.
Unlock with Pro