liveBook · Manning

Durability

Durability is the ability of data, state, or a system to remain preserved, usable, or effective over time despite failures or change.

How 8 Manning books explain it

Kafka for Architects

Durability is the property that acknowledged data survives failures and remains available for later retrieval.

How it is used
Frames the choice between protecting acknowledged Kafka data and keeping partitions available during broker failures.
How deep it goes
Explains persistence, replication, acknowledgments, offset commits, and failure trade-offs; stops short of a low-level storage walkthrough.
Examples
Contrasts payment processing with log collection and compares their data-safety and uptime priorities in a settings table.
What you can do after
Operate/configure it by choosing replica, acknowledgment, and offset-commit settings according to acceptable data-loss and downtime risks.

Read how Kafka for Architects explains durability →

Microservices Patterns, Second Edition

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

How it is used
Uses durability as an ACID guarantee for system commands and as a message-channel selection requirement.
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.

Read how Microservices Patterns, Second Edition explains durability →

The Art of Code

Durability in code is the capacity to remain understandable, useful, and resilient as the surrounding system changes over time.

How it is used
Frames durability as the shared purpose of design, resilience, testing, and trustworthy interfaces.
How deep it goes
Explains durability through architecture, separation of concerns, resilience, testing, and public contracts, with practical design guidance.
Examples
Uses spaghetti, lasagna, ravioli, hexagonal architecture, null checks, explicit absence, APIs, and semantic versioning.
What you can do after
Build durable systems by separating concerns, limiting coupling, preserving behavior, and stabilizing public contracts.

Read how The Art of Code explains durability →

Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

Durability is the likelihood that stored data remains intact and recoverable over a specified period despite failures.

How it is used
Guides storage and recovery decisions for AWS web applications facing instance or Availability Zone failures.
How deep it goes
Defines durability, contrasts it with availability, and explains EBS recovery strategies without detailing durability algorithms or guarantees beyond examples.
Examples
Uses EBS-hosted Jenkins, cross-zone instance replacement, EBS snapshots, S3, and EFS file storage as concrete examples.
What you can do after
Evaluate storage choices and configure recovery using managed services, EBS snapshots, AMIs, or multi-zone file storage.

Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains durability →

Think Distributed Systems

Durability is a transaction property requiring committed effects to persist despite subsequent failures.

How it is used
Protects committed transaction results and dependable promises in business processes.
How deep it goes
Defines permanence after commit and contrasts reliable theoretical systems with failure-prone practical systems.
Examples
Uses payment confirmation followed by shipping as its concrete failure scenario.
What you can do after
Evaluate whether committed transactions can safely support later actions despite component failure.

Read how Think Distributed Systems explains durability →

Decision Engineering

The ability of a system to preserve data or completed operations despite failures or interruptions.

How it is used
Frames acceptable data loss by failure scenario to guide architectural choices.
How deep it goes
Defines four durability tiers through their failure guarantees and architecture implications, including latency and complexity trade-offs.
Examples
Contrasts rebuildable search indexes and temporary data with source-of-truth order and customer records.
What you can do after
Evaluate durability needs by identifying tolerable loss, failure scenarios, and recovery paths.

Read how Decision Engineering explains durability →

MongoDB 8.0 in Action, Third Edition

Data durability is the property that committed data remains recoverable after process termination or system failure.

How it is used
Protects committed MongoDB transaction data during crashes while supporting reliable applications and high-availability deployments.
How deep it goes
Defines durability through ACID, explains journal-and-checkpoint recovery, and extends treatment to replication and concern configuration.
Examples
Uses a flight-and-hotel booking, journal replay after an unexpected exit, replica failures, and majority concern settings.
What you can do after
Configure journaling-related storage settings, replication, and read/write concerns for application-specific durability and availability requirements.

Read how MongoDB 8.0 in Action, Third Edition explains durability →

Apache Kafka in Action

Data durability is the ability of stored data to remain preserved and recoverable despite failures or restarts.

How it is used
Frames Kafka reliability around preserving stored data through replication and producer mechanisms during broker failures.
How deep it goes
Defines durability, distinguishes it from availability and consistency, and previews replication, acknowledgments, idempotence, and transactions without detailing their configuration.
Examples
Uses a three-broker cluster, a sudden broker failure, and horizontal scaling as concrete durability scenarios.
What you can do after
Evaluate how replication and failure-oriented design preserve Kafka data when individual brokers fail.

Read how Apache Kafka in Action explains durability →

Also covered in

What to know first

Related concepts

Questions about durability

What is durability?

Durability is the ability of data, state, or a system to remain preserved, usable, or effective over time despite failures or change.

Which Manning books explain durability?

Kafka for Architects, Microservices Patterns, Second Edition, The Art of Code, Amazon Web Services in Action, Third Edition: An in-depth guide to AWS, Think Distributed Systems, Decision Engineering, MongoDB 8.0 in Action, Third Edition and Apache Kafka in Action.

What should I know before learning durability?

Manning books that teach durability usually introduce availability zone, commit, data loss and availability first.

What is the difference between durability and availability?

Durability is the ability of data, state, or a system to remain preserved, usable, or effective over time despite failures or change. Availability is the degree or proportion of time that a system or service is operational and accessible when required.

What is durability a kind of?

Durability is a kind of service tier dimension. A service tier dimension is a characteristic used to describe or compare the service needs of a system.

What is durability part of?

Durability is part of ACID. ACID is the set of database transaction properties—atomicity, consistency, isolation, and durability—that characterize reliable transactional behavior.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.