exactly-once semantics

A guarantee that each message's effects happen exactly once, even when senders retry or consumers crash.

In more detail

It needs the output and the record of progress to be saved atomically, usually with transactions, plus deduplication of retries. Effects in systems outside the transaction, such as sending an email, still need idempotent handling.

Example

Kafka builds it from idempotent producers, transactions and read_committed consumers.

Related terms

Taught in

References

Certification courses