liveBook · Manning

Persistence

As explained in Microservices Patterns, Second Edition

Message persistence is the storage of messages so they survive broker crashes or restarts.

Message persistence means messages survive broker crashes. Assess it as a requirement for each channel before choosing a messaging technology. It differs from durability, which asks whether messages sent while a consumer was disconnected remain available when it reconnects. section 8.3.3

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines persistence as survival across broker crashes, but does not describe storage mechanisms or broker-specific configuration.
What you can do after
Evaluate broker choices by deciding whether each channel must retain messages through broker crashes.
How it connects
Connects persistence to message-channel requirements, delivery guarantees, durability, and asynchronous service collaboration.

Also explained in

Compare how 12 books explain persistence →

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.