redis-cache-patterns

What problem does it solve?

Redis caching reduces Firestore reads and improves response latency. However, Redis introduces concerns around max connections, network egress costs, and failure handling.

Core Features & Use Cases

• Singleton Pattern with Lazy Connection: ensure a single Redis client is created with fast fail and circuit-breaker ready for resilience.
• Circuit Breaker: temporarily disable Redis on repeated failures to avoid cascading outages.
• Timeouts and Fire-and-Forget Writes: enforce quick read timeouts and non-blocking cache writes to preserve latency.
• Cache-Aside / Read-Through: automatically populate cache on miss and invalidate on updates.
• Graceful Degradation: fallback to the primary datastore (Firestore) when Redis is unavailable.

Quick Start

Initialize a singleton Redis client, wrap reads in a 300ms timeout, and perform non-blocking cache writes to enable graceful degradation.