Delivery guarantee
A delivery guarantee specifies the conditions and semantics governing whether and how messages or records reach consumers and are processed, including behavior under failures or retries.
Kafka for Architects
A delivery guarantee is a defined assurance about whether and how messages are delivered, retained, and processed despite failures or retries.
- How it is used
- Frames message preservation and processing as an architectural concern in asynchronous, event-driven systems.
- How deep it goes
- Explains producer, broker, retention, and consumer failure modes, then connects them to configuration-based guarantees.
- Examples
- Uses lost acknowledgments, replicated writes, consumer retries, Customer 360 producer settings, and compacted topics as concrete examples.
- What you can do after
- Evaluate Kafka producer configurations and failure paths for potential loss, duplication, reprocessing, and ordering effects.
Microservices Patterns, Second Edition
A delivery guarantee specifies the conditions under which a messaging system delivers messages to consumers.
- How it is used
- Define a message channel’s delivery requirement before selecting its messaging technology.
- How deep it goes
- Names best-effort and at-least-once delivery, focusing on requirements rather than delivery mechanics.
- Examples
- Uses best-effort and at-least-once as examples of delivery requirements.
- What you can do after
- Evaluate a channel’s delivery needs before choosing a messaging technology.
Read how Microservices Patterns, Second Edition explains delivery guarantee →
Also covered in
What to know first
- follower nodeA follower node is a non-primary replica that receives replicated data or state from a leader and generally does not initiate leadership.
Related concepts
- data lossaddresses · Data loss is the destruction, corruption, deletion, or unavailability of information that is expected to be retained or remain usable.
- redundancyaddresses · Redundancy is the presence or provision of duplicated or overlapping information, components, resources, or capabilities.
- acknowledgment strategyconfigured by · An acknowledgment strategy is a producer-side policy determining when a published message is acknowledged and what delivery guarantee applies.
- at-most-once deliveryincludes · At-most-once delivery is a messaging guarantee that each message is delivered no more than once, so messages may be lost but are not duplicated.
Questions about delivery guarantee
What is delivery guarantee?
A delivery guarantee specifies the conditions and semantics governing whether and how messages or records reach consumers and are processed, including behavior under failures or retries.
Which Manning books explain delivery guarantee?
Kafka for Architects and Microservices Patterns, Second Edition.
What should I know before learning delivery guarantee?
Manning books that teach delivery guarantee usually introduce follower node first.
What kinds of delivery guarantee are there?
Kinds of delivery guarantee include at-most-once delivery.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

