liveBook · Manning

Durability

As explained in Microservices Patterns, Second Edition

The transaction property that preserves committed changes despite subsequent failures or restarts.

For a transaction, durability means committed effects are permanent and survive crashes or restarts. It is one of the ACID properties used to make system commands transactional. section 9.1.1

Messaging uses a related but distinct channel requirement:

  • A durable channel makes messages sent while a consumer is disconnected available when it reconnects. This differs from persistence, which asks whether messages survive broker crashes. section 8.3.3

In a microservice workflow, local participant transactions can provide ACID guarantees, but a saga spanning services is not itself an ACID transaction. section 9.4

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines committed transaction effects as permanent across crashes or restarts, and distinguishes consumer-reconnect retention from broker-crash persistence.
Examples
Shows a system command that reads products, updates available credit, and inserts an order within a transaction.
What you can do after
Evaluate whether committed command changes or messages for disconnected consumers must survive failures or reconnection.
How it connects
Connects durability to ACID transactions, sagas, and asynchronous message channels.

Also explained in

Compare how 8 books explain durability →

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.