delivery semantics
The promise a messaging system makes about how many times each message is delivered: at most once, at least once or exactly once.
In more detail
Stronger promises cost more coordination. The choice usually comes down to when a consumer records its progress relative to doing the work.
Example
For a Kafka consumer: commit before processing for at-most-once, after for at-least-once.Related terms
- at-most-once delivery — A delivery guarantee in which each message is processed once or not at all, never twice.
- at-least-once delivery — A delivery guarantee under which every message arrives, but some may arrive more than once.
- exactly-once semantics — A guarantee that each message's effects happen exactly once, even when senders retry or consumers crash.
Taught in
- The Payment That Was Charged Twice — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Retry That Overtook — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Two Copies Of One Service — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- At Most Once, At Least Once — Apache Kafka & Event Streaming
- Duplicates Are The Default — Apache Kafka & Event Streaming