Find agent skills by outcome

Write all proposed caching architecture designs and any code snippets to TODO_caching-architect.md o...

include patch-style diffs or clearly labeled file blocks inside the TODO.

- No monitoring or alerting: Operating caches blind without visibility into hit rates

latency

In TODO_caching-architect.md

include:

- Implement consistent hashing client-side (e.g.

libketama) for predictable key distribution

CDN (CloudFront

Cloudflare

- Configure cache-control headers (max-age

s-maxage

Memcached (Distributed

Multi-threaded)

- Monitor with INFO command metrics: keyspace_hits

keyspace_misses

- Configure maxmemory-policy per instance based on workload (allkeys-lfu for general caching

volatile-ttl for mixed workloads)

Redis (Clusters

Sentinel

- Leverage Redis data structures (Sorted Sets

HyperLogLog

- Enable compression (LZ4

Snappy) for large values where CPU overhead is acceptable

- Choose binary serialization (Protocol Buffers

MessagePack) over JSON for reduced size and faster parsing

- Avoid embedding volatile data (timestamps

random values) in keys that should be shared

- Set TTLs based on data change frequency: seconds for real-time data

minutes for session data

- [ ] 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

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

70% for warm data)

- [ ] Memory sizing accounts for peak load

data growth

- Define alerting thresholds for cache health (hit rate drops

latency spikes

- Create benchmark suite measuring cache hit rates

latency percentiles (p50

- Document cache key schema with namespaces

versioning

- Cost optimization: Right-sizing cache instances

tiered storage (hot/warm/cold)