failure-engineering

A circuit breaker pattern prevents cascading failures by blocking requests to a failing dependency, allowing it to recover. This Skill guides implementing circuit breakers alongside fallbacks and retries to manage network instability gracefully without crashing your service.

Graceful degradation keeps software running by providing partial functionality, like cached data or default responses, when a dependency fails. This Skill helps design systems that anticipate dependency unavailability and fail gracefully instead of crashing completely.

Idempotency in distributed systems is needed when network instability causes retries or duplicate message deliveries. This Skill reviews critical write operations, ensuring repeated requests produce the same result without corrupting data or crashing the application.

Chaos engineering tests fault tolerance by proactively injecting failures into a system to identify hidden weaknesses. This Skill guides resilience testing practices, simulating dependency failures and network instability to verify your fault tolerance strategies work under stress.

Handling network instability requires implementing retry mechanisms with proper backoff strategies and dead-letter queues for failed messages. This Skill ensures your service either uses cached data, returns default responses, or fails gracefully when external APIs become unavailable.

Your service crashes because it lacks graceful degradation strategies for dependency failure scenarios. This Skill fixes it by guiding the implementation of circuit breakers, fallbacks, and dead-letter queues to manage cascading errors and maintain continued operation.