Index of every page on this site: llms.txt
All skills
proyecto26 avatar

/resilience-failure

@228d57d
Run it yourself

This skill should be used when the user asks about "fault tolerance", "resilience", a "circuit breaker", "graceful degradation", "retry storm" or "thundering herd on recovery", "exponential backoff with jitter", "timeout", "bulkhead", a "single point of failure" (SPOF), "failover", or "rate limiting" (token bucket / leaky bucket / sliding window). Use it whenever a design must keep working through node crashes, slow dependencies, traffic spikes, or partial outages — i.e. any time the answer to "what happens when this breaks?" is missing, even if the user doesn't say "resilience".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

referencesprovidersazure.md

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

Resilience & failure — Azure

Service mapping

  • Redundancy / failover — Availability Zones within a region (default fault isolation); Availability Sets for rack/update-domain spread; paired-region replication for region loss. VM Scale Sets replace failed instances; Load Balancer / Application Gateway stop routing to unhealthy backends (health probes → load-balancing).
  • Global failover routing — Azure Front Door (and Traffic Manager) for health-probe-based failover and latency/priority routing across regions.
  • Rate limiting / load shedding — Front Door / Application Gateway WAF rate-limit rules at the edge; API Management has throttling policies (rate-limit and quota by key/subscription).
  • Retries / circuit breaking — Azure SDKs retry with backoff + jitter; app-level via Polly (the .NET standard); a mesh (Istio/Linkerd on AKS) adds proxy-level timeouts/retries/breaking.
  • Queue containment — Service Bus (with dead-letter queues) → messaging-streaming.
  • Shared limiter store — Azure Cache for Redis for counters.

Limits / things that bite (verify against current docs)

  • Zone-redundant managed services failover in seconds; async geo-replication (e.g. SQL geo-replicas) can lose recent writes on region failover.
  • API Management rate-limit policies are scoped (by key/product/subscription) and per-unit/region — limits don't automatically aggregate across regions.
  • Front Door WAF rate limiting uses a rolling window with coarse granularity; not a precise per-second limiter.

Provider-specific trade-offs

  • Zone redundancy is the cheap default; paired-region / active-active is a major cost and complexity jump — tie it to the SLA, not ambition.
  • Front Door centralizes edge protection + global routing but becomes a critical path component to design redundantly around.

Pitfalls

  • Confusing Availability Sets (fault/update domains in one datacenter) with Zones (separate datacenters) — only zones survive a datacenter loss.
  • Stacking SDK retries with Polly retries with mesh retries (load multiplier).
  • Treating geo-replication failover as lossless.

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

    The skill provides architectural guidance for system resilience and failure handling. It contains no executable code, network operations, or sensitive data access.

  • 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/resilience-failure