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.

referencesprovidersazure.md

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

Caching — Azure

Service mapping

  • Azure Cache for Redis — managed Redis; tiers: Basic (single node, no SLA), Standard (two-node replicated), Premium (clustering, persistence, VNet, zone redundancy), Enterprise / Enterprise Flash (Redis Enterprise: active geo-replication, RediSearch/modules, NVMe flash for larger-than-RAM sets).
  • Azure Front Door / CDN — edge caching for static/media (→ content-delivery).

When to pick which

Standard for basic HA; Premium for clustering + persistence + VNet isolation; Enterprise for active-active geo-replication or Redis modules; Enterprise Flash when the dataset is large and cost/GB matters more than pure RAM speed.

Limits / things that bite (verify against current docs)

  • Clustering and persistence are Premium+ only — the cheaper tiers are a single logical node.
  • Scaling tiers/clusters can require a failover or a brief data flush; plan for it.
  • Per-tier caps on connections, bandwidth, and memory — a hot key still saturates one shard.
  • Geo-replication semantics differ between Premium (passive) and Enterprise (active) — know which consistency you're getting.

Pitfalls

  • Choosing Basic/Standard then discovering clustering needs a tier jump (migration).
  • Assuming persistence exists below Premium.
  • Lock-in via Enterprise modules (RediSearch etc.) that aren't in open-source Redis.

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