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.

referencesprovidersgcp.md

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

Caching — GCP

Service mapping

  • Memorystore for Redis / Valkey — managed Redis; Basic tier (single node) and Standard tier (replicated with automatic failover); read replicas for read scaling; Cluster mode for sharded horizontal scale.
  • Memorystore for Memcached — managed Memcached; auto-scaled nodes for a simple distributed object cache.
  • Cloud CDN — edge caching for static/media (→ content-delivery).

When to pick which

Redis Standard for HA + failover and data structures; Redis Cluster when one node isn't enough; Memcached for a plain horizontally-scaled object cache; read replicas when reads dominate but the dataset fits one shard.

Limits / things that bite (verify against current docs)

  • Basic tier has no failover and no SLA — a node restart loses the cache.
  • Instances are regional and VPC-attached; cross-region access adds latency.
  • Per-instance memory and network throughput caps; a hot key saturates one shard.
  • Maintenance windows can cause brief failovers — design for transient unavailability.

Pitfalls

  • Using Basic tier in production and being surprised by data loss on maintenance.
  • Forgetting Memorystore is regional — multi-region needs your own replication.
  • Assuming Memcached tier offers persistence/replication (it doesn't).

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