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.

referencesprovidersgcp.md

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

Resilience & failure — GCP

Service mapping

  • Redundancy / failover — regional (multi-zone) Managed Instance Groups are the default fault isolation; multi-region for region loss. MIG autohealing replaces failed instances; the global external HTTP(S) Load Balancer routes around unhealthy backends (health checks → load-balancing).
  • Global failover routing — the global LB + Cloud DNS route to the nearest healthy backend and fail over across regions automatically.
  • Rate limiting / load shedding — Cloud Armor rate-based ban rules and WAF at the edge; Apigee / API Gateway for per-key quota and spike-arrest (token-bucket-style) throttling.
  • Retries / circuit breaking — Cloud client libraries retry with backoff + jitter; Traffic Director / Anthos Service Mesh (Envoy) adds proxy-level timeouts, retries, circuit breaking, and outlier ejection.
  • Queue containment — Pub/Sub (with dead-letter topics) → messaging-streaming.
  • Shared limiter store — Memorystore (Redis) for counters.

Limits / things that bite (verify against current docs)

  • Regional MIGs survive a zone loss transparently; multi-region failover depends on async cross-region replication and can lose recent writes.
  • Cloud Armor rate-based rules use a rolling window with coarse granularity and a configurable ban duration — not a precise per-request limiter.
  • Apigee spike-arrest smooths bursts (per-second/minute) and is enforced per message processor, so effective limits can differ from the nominal rate.

Provider-specific trade-offs

  • GCP's global anycast LB makes multi-region front-ends simpler than elsewhere — but the data tier's replication/consistency is still the hard part (→ consistency-coordination).
  • Regional redundancy is the cheap default; multi-region is the cost/complexity step-up to justify against the SLA.

Pitfalls

  • Deploying a zonal (not regional) MIG and losing everything when that zone fails.
  • Stacking client-library retries with mesh retries (load multiplier).
  • Relying on Cloud Armor for fine-grained per-user limits — use Apigee/app-level.

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