liveBook · Manning

State persistence

As explained in Kafka for Architects

Message persistence is the durable storage of messages beyond the lifetime of the process that produced or consumed them.

Kafka message persistence stores messages on broker disks rather than in memory. Brokers replicate messages, helping the cluster retain them through a broker failure; consumers can resume after disconnection or replay stored messages. section 1.4.2 section 1.7.3

Retention may be configured for a set duration or indefinitely. Unlike systems that remove messages after consumer acknowledgment, Kafka removes data when its retention period expires—even if it has not been processed. Align retention with application needs and monitor disk capacity. section 5.2.5

How Kafka for Architects covers it

How deep it goes
Defines broker storage, replication, retention, and consumer recovery, without detailing storage internals.
Examples
Uses broker failure and disconnected consumers to illustrate recovery, and contrasts retention expiry with acknowledgment-based deletion.
What you can do after
Operate/configure retention to match application needs, monitor disk use, and account for expiry regardless of processing.
How it connects
Connects message persistence to replication, consumer acknowledgments, replay, retention, and event sourcing.

Also explained in

Compare how 7 books explain state persistence →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kafka for Architects. The section links point to the parts of the book it draws on.