Concept
Exactly-once delivery (a myth)
No system can promise that a message is delivered exactly once when networks and processes can fail, because the sender cannot tell a lost message from a lost acknowledgement. What can be built is an exactly-once effect: deliver at least once, and make the processing idempotent so that a repeat changes nothing. Products that advertise exactly-once do this inside their own boundary, and the guarantee ends where your own side effects begin.
Where you'll see it
Related concepts
Sources: Apache Kafka documentation: message delivery semantics ↗ · Segment: Delivering billions of messages exactly once ↗ · KIP-98: Exactly once delivery and transactional messaging ↗ · Report a problem
The definition is in our own words; the sources are those of the lesson Offsets & at-least-once.