CoursesBuilding Scalable Services
Queues and Workers
A work queue against a stream, consumer groups and the visibility window, work that must happen later, and the outbox that keeps a database write and its event together.
- Lessons
- 6
- Exercises
- 35
- Minutes
- 37
- 1
A Work Queue or a Stream
After this lesson you can tell a job that one worker must do from an event that many consumers may read, and pick the queue shape and retention that matches.
Fill blankMultiple choiceShort answer - 2
Consumer Groups and the Visibility Window
After this lesson you can scale consumers without double-processing, set a visibility window from the job's real duration, and read the symptoms of a window that is too short or too long.
DebugMultiple choiceShort answerTrace - 3
Work That Must Happen Later
After this lesson you can schedule a job for a future moment, cancel one that is no longer needed, and build a recurring schedule that survives a restart and never runs twice.
DebugMultiple choiceTrace - 4
The Transactional Outbox
After this lesson you can keep a database write and the event about it together, so no event is published for a write that rolled back and no committed write goes unannounced.
DebugCode orderMultiple choiceTrace - 5
Checkpoint: Queues and WorkersCheckpoint
Queues, streams, visibility, delays and the outbox for a system you have not seen before.
DebugMultiple choiceShort answer - 6
Boss: The Order PipelineBoss
One design carried from the ask to the incident: the question, the estimate, the event contract, queue or stream, the burst that idled the workers, the orders that were billed but never announced, the revised pipeline, and the tradeoff you have to defend.
Code orderMultiple choiceShort answerTrace