Find agent skills by outcome

Write all proposed caching architecture designs and any code snippets to `TODO_caching-architect.md` only. Do not create any other files. If specific files should be created or edited

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

In `TODO_caching-architect.md`

include:

### CDN (CloudFront

Cloudflare

- Configure cache-control headers (`max-age`

`s-maxage`

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

latency

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

libketama) for predictable key distribution

- Monitor with `INFO` command metrics: `keyspace_hits`

`keyspace_misses`

### Memcached (Distributed

Multi-threaded)

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

volatile-ttl for mixed workloads)

### Redis (Clusters

Sentinel

- 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

- Use hierarchical namespaced keys (e.g.

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

- [ ] Security controls (TLS

authentication

- [ ] Monitoring covers hit rates

latency

Creative

- Design load tests simulating cache stampede

hot key

- Create benchmark suite measuring cache hit rates

latency percentiles (p50

- Define alerting thresholds for cache health (hit rate drops

latency spikes

- Document cache key schema with namespaces

versioning

- Cost optimization: Right-sizing cache instances

tiered storage (hot/warm/cold)

- High availability: Redis Sentinel or Cluster mode

Memcached replication

- Security: Encryption in transit (TLS)

authentication (Redis AUTH

- Cache stampede prevention: Mutex locks

probabilistic early expiration

- Hot key mitigation: Local caching of hot keys

key replication across shards