Part 1 of 7 · 1 min read
Why this page comes second
In this module you will
- Define at most once, at least once and exactly once, and say what each costs.
- Show where in a message's journey a duplicate or a loss can happen.
- Explain why exactly-once delivery does not exist, and what people mean by exactly-once processing.
- Make an operation idempotent with a unique id or a stored position.
- Pick a guarantee for a given job and justify it.
Page 1 ended with a worrying detail: a consumer can finish its work, crash before it acknowledges, and receive the same message again. Every real messaging system has to answer what it promises in such cases. This page explains the three standard answers and the one habit, idempotent consumers, that makes the useful one safe. The books used are "Understanding Distributed Systems", "Designing Data-Intensive Applications", "Building Microservices" and "Fundamentals of Software Architecture". The numbers are made up to show the idea, unless the text names a book.