at-most-once delivery
A delivery guarantee in which each message is processed once or not at all, never twice.
A crash between commit and processing silently loses records.
In more detail
A consumer gets it by recording its progress before doing the work. If it crashes in between, those messages are skipped on restart and lost.
Example
Kafka: call consumer.commit() before processing each record.Related terms
- 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.
- at-least-once delivery — A delivery guarantee under which every message arrives, but some may arrive more than once.
- committed offset — The offset a consumer group has saved on the broker for a partition, marking the next record it should read after a restart.
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
- Too Slow Between Two Polls — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- At Most Once, At Least Once — Apache Kafka & Event Streaming