caching-strategy-designer

What problem does it solve?

This Skill helps you decide whether a cache is justified, what data it should hold, and how to keep it correct under real write patterns, tenant boundaries, and failure conditions.

Core Features & Use Cases

• Candidate Qualification: Evaluates read/write ratio, miss cost, cardinality, and staleness tolerance before approving a cache.
• Correctness-First Design: Defines key schemas, tenant scoping, invalidation strategy, stampede protection, and failure behavior before implementation.
• Operational Safeguards: Covers hit-ratio targets, stale-data monitoring, cold-start mitigation, and removal criteria when caching is not worth the risk.
• Use Case: A hot pricing endpoint with frequent reads and daily updates needs a distributed cache with tenant-qualified keys, event-driven invalidation plus backstop TTL, and a clear max-staleness policy.

Quick Start

Ask for a cache design for your workload, including candidate qualification, key structure, invalidation, stampede protection, and failure semantics.