Layer caching with explicit invalidation

Steps

1. 1Classify data: immutable (cache forever), mutable-TTL, never-cache (money)
2. 2Cache at CDN for anonymous GETs with stale-while-revalidate
3. 3Memoize expensive computed objects in-process with short TTL
4. 4Use Redis for shared cross-instance state; set TTLs on everything
5. 5Invalidate by key pattern on write events, not manual flushes
6. 6Monitor hit-rate per layer; below 60% means wrong layer or wrong keys

Common Pitfalls

• ▲Caching authenticated responses at shared CDN edge
• ▲Thundering herd on expiry without jitter or locks

Commands

$ npx skills add aniruddhaadak80/skills --skill caching-queues-cache-strategy-layers

$ npx skills add aniruddhaadak80/skills --skill caching-queues-cache-strategy-layers -g

Tags