Index of every page on this site: llms.txt
All skills
Run it yourself

This skill should be used when the user asks about a "caching strategy", "cache invalidation", "what to cache", "read-through vs write-through vs write-back", "cache eviction" (LRU/LFU/TTL), "Redis vs Memcached", "stale reads", or hits "thundering herd", "cache stampede", "cache penetration", or "hot key" problems, or is choosing a Redis `maxmemory` eviction policy (allkeys-lru, volatile-lru, noeviction) vs TTL expiry for sessions or other cached state. Use it whenever a design is read-heavy or a datastore is overloaded by reads, even if the user doesn't say "cache".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/caching

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersgeneric.md

≈438 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Caching — generic / self-hosted

The vendor-neutral default. When no cloud is named, this is the answer.

What to run

  • Memcached — multithreaded LRU object cache; simplest, highest raw throughput for get/set. No persistence, no replication, no rich types.
  • Redis (open source / Valkey) — single-threaded core, rich data structures, optional persistence (RDB/AOF), replication, and Redis Cluster for horizontal sharding via hash slots (16,384 slots, consistent-hash-like).

Topology

  • Single node for small hot sets.
  • Primary + replicas for read scaling and failover (replica promotion on primary loss; expect a brief unavailability + possible loss of un-replicated writes).
  • Cluster mode (sharded) when the hot set or QPS exceeds one node. Client or proxy routes keys to shards by hash slot.

Limits / things that bite

  • A node is bounded by RAM (the hot set must fit) and by a single core for Redis command execution — a hot key can saturate one shard regardless of total cluster size. Mitigate with an L1 tier or key replication (see deep-dive).
  • Persistence (AOF fsync) trades durability for write latency; RDB snapshots can cause fork/latency spikes on large datasets.
  • Eviction is configured per instance (maxmemory-policy: allkeys-lru, volatile-ttl, etc.) — set it deliberately; the default may reject writes when full.

Pitfalls

  • No managed failover — you operate Sentinel/Cluster yourself.
  • Cluster mode restricts multi-key ops to a single slot (hash tags needed).
  • Backups/persistence and security (TLS, auth) are on you.

Operationally heavier than a managed service, but zero lock-in and full control. Use when running your own infra or for portability across clouds.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    This skill is a pure documentation and architectural guidance resource for system design, specifically focusing on caching strategies and failure modes across various cloud providers. It contains no executable code, network operations, or security risks.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/caching