Nestjs caching

Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/nestjs-caching

🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.

Install

npx -y skills add ComeOnOliver/skillshub --skill nestjs-caching

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Multi-level caching, Invalidation patterns, and Stampede protection. Use when implementing multi-level caching or cache invalidation strategies in NestJS. (triggers: **/*.service.ts, **/*.interceptor.ts, CacheInterceptor, CacheTTL, Redis, stale-while-revalidate)

SKILL.md

2.7 KB, as published. Nobody here has run it

Caching & Redis Standards

Priority: P1 (OPERATIONAL)

Caching strategies and Redis integration patterns for high-performance NestJS applications.

Caching Strategy

Layering: Use Multi-Level Caching for high-traffic read endpoints.
- L1 (Local): In-Memory (Node.js heap). Ultra-fast, no network. Ideal for config/static data. Use lru-cache.
- L2 (Distributed): Redis. Shared across pods.
Pattern: Implement Stale-While-Revalidate where possible to avoid latency spikes during cache misses.

NestJS Implementation

Library: Use cache-manager with cache-manager-redis-yet (Recommended over cache-manager-redis-store for better V4 support and stability).
Interceptors: Use @UseInterceptors(CacheInterceptor) for simple GET responses.
- Warning: By default, this uses the URL as the key. Ensure consistent query param ordering or custom key generators.

Decorators: Standardize custom cache keys.

@CacheKey('users_list')
@CacheTTL(300) // 5 minutes
findAll() { ... }

Redis Data Structures (Expert)

Don't just use GET/SET.
Hash (HSET): Storing objects (User profiles). Allows partial updates (HSET user:1 lastLogin result) without serialization overhead.
Set (SADD): Unique collections (e.g., "Online User IDs"). O(1) membership checks.
Sorted Set (ZADD): Priority queues, Leaderboards, or Rate Limiting windows.

Invalidation Patterns

Problem: "There are only two hard things in Computer Science: cache invalidation and naming things."
Tagging: Since Redis doesn't support wildcards efficiently (KEYS is O(N) - bans in PROD), use Sets to group keys.
- Create: SADD post:1:tags cache:post:1
- Invalidate: Fetch tags from Set, then DEL usage keys.
Event-Driven: Listen to Domain Events (UserUpdated) to trigger invalidation asynchronously.

Stampede Protection

Jitter: Add random variance to TTLs (e.g., 300s ± 10s) to prevent all keys expiring simultaneously.
Locking: If a key is missing, one process computes it while others wait or return stale. (Complex, often handled by swr libraries).

Anti-Patterns

No KEYS in production: Use SET-based tag grouping for cache invalidation; KEYS is O(N).
No fixed TTLs on grouped caches: Add jitter (±10s) to prevent simultaneous stampede.
No MemoryStorage for multi-pod: Use Redis store; in-memory cache is not shared across pods.