add-redis-cache

Implement tenant-isolated Redis caching with cache-aside strategy for Lambda microservices.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/tcelestino/softplan-engineering-skills --skill add-redis-cache
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-redis-cache
Source: https://github.com/tcelestino/softplan-engineering-skills/tree/main/skills/add-redis-cache
Command: npx skills add https://github.com/tcelestino/softplan-engineering-skills --skill add-redis-cache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ElastiCache Redis connections are frequently created per invocation, leading to latency, cold starts, and connection churn. This Skill introduces a reusable Redis client and tenant-scoped sessions combined with a cache-aside layer to improve performance and data isolation across Lambda-based microservices.

Core Features & Use Cases

  • Reusable Redis client across Lambda invocations to reduce connection overhead and warm-start costs.
  • Tenant-isolated SessionService to prevent cross-tenant data leakage and track user context.
  • CacheService with a namespace-based cache, TTLs, and cache-aside pattern to accelerate reads and simplify data synchronization.
  • Use Case: Attach to existing services created with create-lambda-service to add fast in-process caching and robust session management.

Quick Start

Integrate the provided Redis client, session service, and cache service into your existing Lambda microservice to enable tenant-isolated sessions and cache-aside caching.

Frequently Asked Questions about add-redis-cache

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

FAQPage Schema
How do I reduce Redis connection churn and latency in AWS Lambda?

You can reduce Redis connection churn in Lambda by using a reusable Redis client across invocations. This prevents creating new ElastiCache connections per execution, lowering warm-start costs and connection overhead.

What is the cache-aside pattern and how does it work with Redis?

The cache-aside pattern with Redis accelerates reads by checking the cache first and loading data only on a miss. It uses namespace-based keys and TTLs to simplify data synchronization and ensure consistency.

How do I isolate session data across tenants in a Lambda microservice?

You isolate tenant sessions by using a tenant-scoped SessionService with namespace-based keys. This tracks user context and prevents cross-tenant data leakage in your Lambda microservices.

Can I add caching to an existing Lambda service without rebuilding it?

Yes, you can integrate a shared Redis client, SessionService, and CacheService into your existing Lambda microservices. This adds in-process caching and session management without requiring a full rebuild.

What are the limitations of using ElastiCache Redis with Lambda?

A key limitation is connection overhead from creating ElastiCache Redis connections per invocation, causing cold starts and churn. Using a reusable client mitigates this, but connection pooling behavior depends on Lambda execution environment reuse.