Timeouts, Retries & Retry Storms
Why naive retries turn a slow service into an outage. Lesson 6 of Level 9: Microservices. Based on Building Microservices, DDD, Software Architecture and DDIA.
Level 9 · Microservices · Lesson 6 of 13
Why naive retries turn a slow service into an outage.
Continue learning
- API Gateways, BFFs & Service Discovery — Previous lesson
- Circuit Breakers & Bulkheads — Next lesson
- Level 9: Microservices — Back to the level
Try it hands-on
- Retry Storm & Backoff with Jitter — Slow a service down and watch naive retries multiply traffic; add backoff, jitter and retry budgets to recover.
- Microservices Lab — Failures, retries, circuit breakers, sagas and idempotency.
All lessons in Microservices
- Why Microservices Exist — and When Not to Use Them
- Finding Service Boundaries & Splitting the Monolith
- Database per Service & Data Ownership
- Synchronous vs Asynchronous Communication
- API Gateways, BFFs & Service Discovery
- Timeouts, Retries & Retry Storms
- Circuit Breakers & Bulkheads
- Idempotency: Making Retries Safe
- Distributed Transactions: 2PC, Sagas & the Outbox
- Observability: Logs, Metrics, Traces & SLOs
- Deployment: Containers, Kubernetes, Canary & Feature Flags
- Testing Microservices & Consumer-Driven Contracts
- Teams, Ownership & Conway’s Law