Make the backend survive its dependencies: timeout every outbound call, retry idempotent-only with exponential backoff + jitter, add circuit breakers and bulkheads, define a graceful-degradation mode, and design idempotent background workers with DLQs and backpressure.
Scanned 9/23/2026
Skills Directorynpx -y skills add mcorbett51090/RavenClaude --skill backend-resilience --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Backend Resilience?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-backend-resilience)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: backend-resilience
description: "Make the backend survive its dependencies: timeout every outbound call, retry idempotent-only with exponential backoff + jitter, add circuit breakers and bulkheads, define a graceful-degradation mode, and design idempotent background workers with DLQs and backpressure."
---
# Backend Resilience
## Timeouts
Every outbound call has one (sized to the dependency's SLO). No timeout = cascading outage.
## Retries
**Idempotent only**, bounded, exponential backoff + **jitter** (avoid synchronized storms). A retry on a non-idempotent call = a duplicate.
## Isolate
**Circuit breaker** (fail fast on a failing dep) + **bulkhead** (one slow dep can't starve the rest).
## Degrade + async
Define the degraded mode (stale cache / queued / clear error). Workers: **idempotent** + **DLQ** + **bounded queue** (backpressure, not unbounded growth).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
