resilience-failure

Analyze system failure modes and apply circuit breakers, bulkheads, and exponential backoff.

42|2|Updated Jun 1, 2026

Search Tags:#resilience #availability #rate-limiting #system-design #circuit-breaker #fault-tolerance

Ready to run

npx skills add https://github.com/proyecto26/system-design-skills --skill resilience-failure-proyecto26

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resilience-failure
Source: https://github.com/proyecto26/system-design-skills/tree/main/skills/resilience-failure
Command: npx skills add https://github.com/proyecto26/system-design-skills --skill resilience-failure-proyecto26

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents cascading failures and system meltdowns by implementing robust patterns to handle node crashes, slow dependencies, and traffic spikes.

Core Features & Use Cases

Failure Containment: Implements circuit breakers, bulkheads, and timeouts to isolate failing components.
Traffic Management: Provides strategies for rate limiting, load shedding, and retry logic with jitter to prevent retry storms.
Use Case: When a microservice dependency becomes slow, this skill guides you to implement a circuit breaker and a graceful degradation fallback, ensuring the user receives a cached response instead of a system error.

Quick Start

Use the resilience-failure skill to analyze the blast radius and define timeout and retry strategies for the payment gateway integration.

Frequently Asked Questions about resilience-failure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent cascading failures in a microservices architecture?▼

Use circuit breakers and bulkheads to isolate failing components. This approach ensures fault isolation and graceful degradation, maintaining high availability during partial outages and preventing system-wide meltdowns.

What is the best way to handle retry storms and thundering herds in distributed systems?▼

Apply exponential backoff with jitter. This traffic management strategy randomizes retry intervals, preventing synchronized client retries from overwhelming dependencies during traffic spikes or slow responses.

When do I need a circuit breaker pattern for fault tolerance?▼

You need a circuit breaker when a microservice dependency becomes slow or unresponsive. It monitors failure rates and trips to stop requests, enabling graceful degradation by returning cached responses instead of system errors.

How do I design a fault-tolerant system with graceful degradation?▼

Combine failure containment patterns like bulkheads and circuit breakers with load shedding. Validate design choices against stress-test scenarios including retry storms and single points of failure to ensure self-healing during partial outages.

Does rate limiting help with system availability during traffic spikes?▼

Rate limiting improves system availability by controlling traffic spikes. Combined with load shedding, it prevents meltdowns by restricting incoming requests, ensuring services remain responsive when dependencies fail or experience sudden surges.