redis-cache-patterns

Implement Redis caching patterns with cache-aside reads, non-blocking writes, and Firestore fallback.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/ducnm-mimhus/Avada-Simple-Sales-Pop --skill redis-cache-patterns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: redis-cache-patterns
Source: https://github.com/ducnm-mimhus/Avada-Simple-Sales-Pop/tree/main/.claude/skills/redis-caching
Command: npx skills add https://github.com/ducnm-mimhus/Avada-Simple-Sales-Pop --skill redis-cache-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about redis-cache-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Redis caching with graceful fallback to Firestore?▼

Redis caching with graceful fallback to Firestore is implemented by wrapping reads in a 300ms timeout and applying a circuit breaker. When Redis becomes unavailable, the circuit breaker trips and routes read requests directly to Firestore.

What is the best way to prevent cascading outages when using Redis caching?▼

Preventing cascading outages during Redis caching failures requires a circuit breaker pattern. This mechanism temporarily disables Redis connections after repeated failures, preserving application stability by stopping repeated timeout attempts.

How do I handle cache invalidation with a read-through Redis pattern?▼

Handling cache invalidation with a read-through Redis pattern involves automatically populating the cache on a read miss and explicitly invalidating the cached data upon subsequent data updates.

How do I reduce Firestore reads and lower latency in microservices?▼

Reducing Firestore reads and lowering latency in microservices is achieved by implementing a cache-aside pattern. This uses a lazy singleton Redis connection with fire-and-forget writes to minimize database access and network egress.

Why do I need a circuit breaker and timeouts for Redis caching?▼

You need a circuit breaker and 300ms read timeouts for Redis caching to enforce quick failure recovery and prevent network delays. This ensures non-blocking cache writes and preserves overall application latency when Redis degrades.

Does this Redis caching pattern work for serverless functions?▼

Yes, this Redis caching pattern works for serverless functions by enforcing lazy singleton connections to manage max connections limits. It applies read-through cache-aside logic and graceful degradation to handle read-heavy workloads efficiently.