Redis Caching with Claude Code: Cache-Aside, Write-Through, and TTL Strategy

APIs without caching run the same DB queries repeatedly. Redis can make responses 10x faster — but wrong cache design causes data inconsistency. Claude Code generates the safe caching patterns from CLAUDE.md rules. CLAUDE.md for Cache Rules ## Redis Cache Design Rules ### Patterns - Cache-Aside: high-read/low-write data (user profiles, product catalog) - Write-Through: data requiring strong consistency (balances, inventory) - Pub/Sub: cache invalidation propagation (distributed environments) ### TTL (required) - All caches must have TTL (no permanent caches) - Master data: TTL 1 hour - Sessions/profiles: TTL 15 minutes - Aggregations: TTL 5 minutes ### Cache Keys - Format: {service}:{entity}:{id} - Examples: user:profile:123, product:detail:abc - Versioning: user:v2:profile:123 (bump version on schema changes) ### Monitoring - Track cache hit ratio as a metric - Design for cold start (unwarmed cache) scenarios Generating Cache-Aside Pattern Generate Cache - Aside cache for user profile