liveBook · Manning

Delivery guarantee

As explained in Microservices Patterns, Second Edition

A delivery guarantee specifies the conditions under which a messaging system delivers messages to consumers.

A delivery guarantee states the delivery conditions required of a message channel. Best-effort and at-least-once are examples of possible requirements. section 8.3.3

Specify the requirement before choosing a messaging technology. Asynchronous service collaboration patterns require at-least-once delivery, alongside other channel capabilities. section 8.3.3

How Microservices Patterns, Second Edition covers it

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.
How it connects
Connects delivery guarantees to message channels, asynchronous messaging, and service collaboration patterns.

Also explained in

Compare how 2 books explain delivery guarantee →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.