Demo: retry storms and jitter
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
show how naive retries make an outage worse. Prepares MID-033-LAB1.
Draft outline details
Step by step
- Run 200 virtual users against
inventorythrough Toxiproxy; make the service fail for 10 seconds. - Add fixed-interval retries (3 attempts, 100 ms) and watch request volume triple and recovery stall.
- Planned mistake: also retry
POST /paymentsautomatically; show a customer charged twice in the test data. Fix: retry only idempotent calls or use an idempotency key. - Switch to exponential backoff with jitter and a limit; compare the request-rate graphs.
- Add a retry budget or breaker so retries stop when the failure rate is high.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.