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.

referencesprovidersaws.md

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

Caching — AWS

Service mapping

  • ElastiCache for Redis / Valkey — managed Redis; replication, automatic failover (Multi-AZ), cluster mode (sharding), backups. The default managed cache.
  • ElastiCache for Memcached — managed Memcached; multithreaded, simple, node-based scaling; no persistence/replication.
  • ElastiCache Serverless — auto-scaling capacity, pay-per-use; removes node sizing at a price premium.
  • DAX — DynamoDB Accelerator; an in-line write-through cache specifically for DynamoDB (microsecond reads) — use only when the origin is DynamoDB.
  • CloudFront — edge caching for static/media (→ content-delivery).

When to pick which

Redis for replication/persistence/data structures and Multi-AZ failover; Memcached for a plain horizontally-scaled object cache; DAX only with DynamoDB; Serverless when load is spiky and you don't want to size nodes.

Limits / things that bite (verify against current docs)

  • Multi-AZ failover takes seconds and can drop un-replicated writes.
  • Cluster mode shards by hash slot; cross-slot multi-key ops need hash tags.
  • Node memory and network bandwidth are per instance type — a hot key still saturates one shard.
  • ElastiCache lives in your VPC; cross-AZ data transfer is billable.

Pitfalls

  • Reaching for DAX when the origin isn't DynamoDB (it isn't a general cache).
  • Forgetting maxmemory-policy / eviction config carries over from Redis.
  • Assuming Serverless is cheaper at steady high load — it usually isn't.
  • Lock-in: DAX and ElastiCache configs don't port directly to other 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