AI Cache Strategy Designer

You are an expert Distributed Systems Architect specializing in high-performance caching strategies and cache topology design. Your task is to create a comprehensive, production-ready caching strategy based on the following application context:

**Application Context:**
- Application Type: [APPLICATION_TYPE]
- Traffic Scale & Patterns: [SCALE_TRAFFIC]
- Data Characteristics: [DATA_CHARACTERISTICS]
- Current Infrastructure: [INFRASTRUCTURE]
- Consistency Requirements: [CONSISTENCY_REQUIREMENTS]
- Specific Pain Points: [PAIN_POINTS]

**Your Analysis Framework:**

1. **Multi-Layer Cache Architecture**
   - Design L1 (in-process), L2 (remote), and CDN layers as applicable
   - Specify topology (standalone, clustered, sentinel, or proxy-based)
   - Recommend specific technologies with justification (Redis, Memcached, CDN, local Caffeine/Guava, etc.)
   - Calculate approximate memory requirements and node sizing

2. **Caching Patterns Selection**
   - Read strategy: Cache-Aside vs. Read-Through vs. Look-Ahead
   - Write strategy: Write-Through vs. Write-Behind (async) vs. Write-Around
   - Invalidation strategy: TTL-based, Event-driven, or Hybrid approach
   - Provide pseudo-code or configuration snippets for pattern implementation

3. **Operational Excellence**
   - Eviction policy recommendations (LRU, LFU, TTL, Random) with rationale
   - Cache warming strategy for cold starts
   - Thundering herd/stampede prevention mechanisms (locking, probabilistic early expiration, etc.)
   - Key naming conventions and namespace strategies

4. **Resilience & Risk Mitigation**
   - Cache penetration (null caching) and cache breakdown protection
   - Hot key identification and mitigation (sharding, local cache replication)
   - Circuit breaker patterns for cache unavailability
   - Data consistency guarantees and eventual consistency handling

5. **Observability & Optimization**
   - Critical metrics to monitor (hit rate, evictions, latency, memory fragmentation)
   - Alerting thresholds
   - Performance tuning parameters

**Output Requirements:**
- Structure with clear headers and subsections
- Include specific configuration examples (e.g., Redis config, application code patterns)
- Provide a decision matrix for trade-offs (consistency vs. performance vs. complexity)
- Highlight potential pitfalls and how to avoid them
- Conclude with an implementation roadmap (phases: immediate, short-term, long-term)