liveBook · Manning

At-least-once delivery

As explained in Microservices Patterns, Second Edition

A message-delivery guarantee in which every message is delivered one or more times, permitting redelivery after failures.

At-least-once delivery guarantees that each message arrives one or more times, allowing redelivery after failures. It is a required message-channel property for asynchronous service collaboration. section 8.3.3

Evaluate delivery guarantees alongside ordering, competing consumers, persistence, durability, scalability, and latency before choosing a broker. This keeps the design decision technology-agnostic. section 8.3.3

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the guarantee as a channel requirement but does not detail its implementation or handling of duplicate deliveries.
Examples
Names ActiveMQ, RabbitMQ, Kafka, Kinesis, SQS, and SNS when comparing broker channel implementations.
What you can do after
Evaluate message-channel requirements before selecting a broker.
How it connects
Connects delivery guarantees with asynchronous messaging, message channels, ordering, competing consumers, persistence, and durability.

Also explained in

Compare how 6 books explain at-least-once delivery →

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.