Redis Caching Patterns

• Read/write hotspots and latency objectives.
• Freshness and consistency constraints.
• Redis memory/eviction limits.
• Failure/degradation expectations.

Deliverables

• Key namespace and TTL/invalidation policy.
• Stampede/hot-key mitigation plan.
• Cache observability and operational guardrails.

Workflow

1. Define cache policy in assets/redis-cache-policy-template.md.
2. Apply freshness/invalidation rules from references/cache-invalidation-rules.md.
3. Validate stampede and hot-key behavior.
4. Define failure behavior for cache misses/outages.
5. Finalize with assets/cache-observability-checklist.md.

Quality Standard

• Key strategy is consistent and ownership is explicit.
• Invalidation policy matches correctness requirements.
• Failure paths preserve system correctness.
• Observability supports rapid cache regression diagnosis.

Failure Conditions

• Stop when invalidation policy cannot satisfy correctness bounds.
• Stop when cache behavior is unobservable in production.
• Escalate when caching introduces tail-latency or error regressions.