Find agent skills by outcome

- Avoid embedding volatile data (timestamps

random values) in keys that should be shared

- [ ] Security controls (TLS

authentication

- Use hierarchical namespaced keys (e.g.

`app:user:123:profile`) for logical grouping and bulk invalidation

- [ ] Monitoring covers hit rates

latency

- [ ] Memory sizing accounts for peak load

data growth

- [ ] Cache hit rates meet target thresholds (typically >90% for hot data

>70% for warm data)

Business

After designing or modifying a caching strategy

verify:

- Define alerting thresholds for cache health (hit rate drops

latency spikes

- Create benchmark suite measuring cache hit rates

latency percentiles (p50

Creative

- Design load tests simulating cache stampede

hot key

- Cost optimization: Right-sizing cache instances

tiered storage (hot/warm/cold)

- Document cache key schema with namespaces

versioning

- Map each data entity to its invalidation strategy (write-through

write-behind

- High availability: Redis Sentinel or Cluster mode

Memcached replication

Business

- Memory management: Eviction policy selection

maxmemory configuration

- Security: Encryption in transit (TLS)

authentication (Redis AUTH

- Cache stampede prevention: Mutex locks

probabilistic early expiration

- Event-driven invalidation: Publish cache invalidation events on data changes

scalable for distributed systems

- Hot key mitigation: Local caching of hot keys

key replication across shards

- Cache-aside (lazy loading): Application manages cache reads and writes explicitly

simple but risk of stale reads

- Write-behind (write-back): Asynchronous batch writes to backing store

lower write latency

- Write-through: Synchronous cache update on every write

strong consistency

- Database caching: Query result caching

materialized views

- Application-level caching: In-process caches (e.g.

Guava