Prompt · Developer Tools

Caching Strategy

Designs a caching layer for a slow read path: what, where, and invalidation.

Have ready: Describe the slow read, freshness needs, and scale

Fill in · 5 fields

WHAT IS QUERIED AND WHY IT IS SLOWREAL-TIME / SECONDS / MINUTES / EVENTUAL, AND WHAT BREAKS IF STALEe.g. 100:1REQUESTS PER SECOND, DATA SIZEFRAMEWORK, DATABASE, INFRA

Your prompt

Design a caching strategy for this read path.

Slow read: [WHAT IS QUERIED AND WHY IT IS SLOW]
Freshness requirement: [REAL-TIME / SECONDS / MINUTES / EVENTUAL, AND WHAT BREAKS IF STALE]
Read/write ratio: [e.g. 100:1]
Scale: [REQUESTS PER SECOND, DATA SIZE]
Stack: [FRAMEWORK, DATABASE, INFRA]

Deliver:
1. What to cache (full responses? query results? computed fragments?) and the cache key design, show actual key patterns.
2. Where: in-process / Redis / CDN, with TTLs and your reasoning for each.
3. Invalidation strategy: TTL-only, write-through, write-behind, or event-driven, and exactly which writes invalidate which keys.
4. The stampede/thundering-herd protection for a cold cache.
5. What you would measure to prove the cache is helping, and the failure mode if the cache goes down.

Call out the one invalidation case most likely to bite me.

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this

Rate Limit Designer

Webhook Handler Template

Breaking Change Check

Retry Logic Review

Edge Case Enumerator

Env Config Audit