Delivery semantics
Also called: delivery guarantees, at most once, at least once, exactly once
Delivery semantics describe the outcomes a messaging system promises under stated failures and assumptions. At-most-once delivery may lose work but avoids redelivery. At-least-once delivery retries uncertain work and can produce duplicates. Exactly-once processing requires a defined boundary within which repeated attempts produce one committed result.
For example, a consumer can update a database and crash before acknowledging its message. Redelivery may repeat the database change unless the application deduplicates or coordinates the two steps. Kafka transactions can coordinate supported Kafka records and offsets; effects in another system require cooperation from that system.
- Further reading
- Apache Kafka — Design: Message Delivery Semantics