Skill

role-backend:caching-strategies

Implements Redis caching patterns like cache-aside, write-through, write-behind; covers Memcached, invalidation strategies, TTL design, stampede prevention, CDN config, distributed caching. For optimizing read performance, reducing DB load, designing cache layers.

Redis

Node

backend

performance

npx claudepluginhub rnavarych/alpha-engineer --plugin role-backend

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/role-backend:caching-strategies

User invocable

Model invocable

Inline context

Default effort

Tool Access

This skill is limited to the following tools:

ReadGrepGlobBash

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

- Choosing a caching pattern for a new feature (cache-aside, write-through, read-through)

Supporting Files

references/patterns-redis-invalidation.mdreferences/stampede-cdn-monitoring.md

SKILL.md

34 lines · ~542 tokens

Similar Skills

caching-strategies

Provides caching patterns like cache-aside, write-through, stampede prevention, CDN headers, multi-level L1/L2/L3 caches, and invalidation strategies for high-traffic systems and CDN design.

5 files3 tools

billy-milligan

cache

Assesses caching opportunities and implements multi-layer strategies with Redis/Memcached/CDN, including cache-aside patterns, TTL/event invalidation, and stampede prevention.

godmode

caching-strategies-knowledge

Provides caching strategies (Cache-Aside, Read-Through, Write-Through, Write-Behind), invalidation approaches, multi-level caching, and Redis data structures for audits and generation.

3 files

acc

Stats

LanguageShell

Parent stars13

Parent forks1

MaintenanceGood

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

role-backend:caching-strategies

Caching Strategies

When to use

Choosing a caching pattern for a new feature (cache-aside, write-through, read-through)

Designing Redis key naming and data structure selection

Building cache invalidation logic that stays consistent under writes

Setting TTLs that balance freshness with database load

Preventing cache stampede on high-traffic cache misses

Configuring CDN headers for static assets and versioned files

Evaluating whether to use Redis vs Memcached

Setting up cache hit rate monitoring and eviction alerts

Core principles

Pattern before implementation — cache-aside, write-through, and write-behind have different consistency trade-offs; pick deliberately

TTL jitter is mandatory at scale — synchronized expiration = thundering herd; add 10-30% random variance

Hit rate is the only real metric — target >90%; anything lower means either wrong keys or wrong TTLs

Stale is often fine — serve stale data while revalidating in background rather than blocking on a miss

Cache is not storage — set maxmemory-policy allkeys-lru and accept eviction; anything that can't be lost belongs in the database

Reference Files

references/patterns-redis-invalidation.md — four caching pattern descriptions (cache-aside, write-through, write-behind, read-through), Redis data structure selection guide, connection management, key naming conventions, and cache invalidation strategies with TTL design

references/stampede-cdn-monitoring.md — cache stampede prevention techniques (mutex, probabilistic expiration, stale-while-revalidate) with Node.js code examples, Memcached use cases, CDN Cache-Control header configuration, and Redis monitoring and operations

Caching Strategies

When to use

Choosing a caching pattern for a new feature (cache-aside, write-through, read-through)
Designing Redis key naming and data structure selection
Building cache invalidation logic that stays consistent under writes
Setting TTLs that balance freshness with database load
Preventing cache stampede on high-traffic cache misses
Configuring CDN headers for static assets and versioned files
Evaluating whether to use Redis vs Memcached
Setting up cache hit rate monitoring and eviction alerts

Core principles

Pattern before implementation — cache-aside, write-through, and write-behind have different consistency trade-offs; pick deliberately
TTL jitter is mandatory at scale — synchronized expiration = thundering herd; add 10-30% random variance
Hit rate is the only real metric — target >90%; anything lower means either wrong keys or wrong TTLs
Stale is often fine — serve stale data while revalidating in background rather than blocking on a miss
Cache is not storage — set maxmemory-policy allkeys-lru and accept eviction; anything that can't be lost belongs in the database

Reference Files

references/patterns-redis-invalidation.md — four caching pattern descriptions (cache-aside, write-through, write-behind, read-through), Redis data structure selection guide, connection management, key naming conventions, and cache invalidation strategies with TTL design
references/stampede-cdn-monitoring.md — cache stampede prevention techniques (mutex, probabilistic expiration, stale-while-revalidate) with Node.js code examples, Memcached use cases, CDN Cache-Control header configuration, and Redis monitoring and operations

role-backend:caching-strategies

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

role-backend:caching-strategies

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

Caching Strategies

When to use

Core principles

Reference Files

Similar Skills

Help us improve

Caching Strategies

When to use

Core principles

Reference Files