Day 6 of 14 35 minCommit orderDuplicatesIdempotence
Find out exactly when events can be lost or processed twice. Compare at-most-once, at-least-once and exactly-once, make producers safe with idempotence, and make consumers safe by designing idempotent processing.
By the end of today you can
- Explain at-most-once, at-least-once and exactly-once processing
- Show how the order of "process" and "commit" decides what a crash does
- Prevent producer duplicates with idempotence
- Make consumers idempotent with event IDs and upserts
- Describe what Kafka transactions do, and their limits
What's inside
- 4 sections
- 3 diagrams and mind maps
- 5 code examples you can run
- 5-question quiz
- 1The order of "process" and "commit"
- 2Producer duplicates: idempotence
- 3Consumer duplicates: make processing idempotent
- 4Exactly-once with transactions
Sign in free to read this lesson
Get the full lesson with diagrams, runnable code and the quiz. Your progress is saved across devices.
Sign in free