Skill

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.

Redis

performance

backend

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Popularity

Parent stars

Parent forks

Invocation

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

Slash command

/billy-milligan:caching-strategies

User invocable

Model invocable

Inline context

Default effort

Tool Access

This skill is limited to the following tools:

ReadGrepGlob

Context Preview

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

- Designing cache layers for high-traffic systems

Supporting Files

assets/caching-checklist.mdreferences/cache-invalidation.mdreferences/caching-patterns.mdreferences/cdn-edge-caching.mdreferences/redis-deep-dive.md

SKILL.md

31 lines · ~358 tokens

Similar Skills

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.

2 files4 tools

role-backend

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

cache

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

godmode

Stats

LanguageShell

Parent stars13

Parent forks1

MaintenanceExcellent

Last CommitMar 5, 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.

Caching Strategies

When to use

Designing cache layers for high-traffic systems

Preventing cache stampede / thundering herd

Setting CDN/HTTP cache headers or cache invalidation strategy

Core principles

Cache-aside is the default — application controls all cache interactions

Always add jitter to TTL — ±10% prevents synchronized expiry stampedes

Cache invalidation is harder than caching — design invalidation FIRST, then TTL

Multi-level cache reduces latency multiplicatively — L1 (in-memory) → L2 (Redis) → L3 (DB)

A cache miss should never cascade to DB overload — use lock-based prevention

References available

references/caching-patterns.md — cache-aside, write-through, write-behind, multi-level with code

references/redis-deep-dive.md — data structures for caching, eviction policies, cluster mode

references/cdn-edge-caching.md — Cache-Control headers, stale-while-revalidate, purge strategies

references/cache-invalidation.md — stampede prevention, event-driven invalidation, versioned keys

Assets available

assets/caching-checklist.md — what to cache, TTL recommendations, monitoring queries