Messaging at scale
On This Lesson 4 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
see what changes when message volume grows by 50 times.
Planned topics
- Small design choices (keys, partitions, batch size) become big cost and reliability factors.
- The broker is shared infrastructure: one noisy topic can hurt others.
- Scale problems show up as lag, rebalances, and recovery time, not only as throughput.
- Plan for catch-up speed, not just steady-state.
Draft outline details
Demonstration
a chart sketch of FulfillCo's partner feed: 50x Shop's order events, daily peaks, and the headroom needed for catch-up.
Check your understanding
Why plan for catch-up speed?
Show answer
After an outage consumers must process backlog plus new events.
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.