Demo: recovering from a six-hour consumer backlog
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
drain a large backlog without breaking live traffic.
Draft outline details
Step by step
- Show lag at six hours after a consumer bug.
- Fix the bug, then scale consumers up to the partition count.
- Check the downstream database as the new bottleneck; add batching.
- Planned mistake: scale consumers beyond partitions and see no gain; fix by increasing parallelism inside the consumer or using more partitions in future design.
- Track time-to-clear against the estimate and record lessons in the runbook.
Prepares SRB-006-LAB1.
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.