Partition tolerance
Partition tolerance is the ability of a distributed system to continue operating despite communication failures between parts of the system.
ScyllaDB in Action
Network partition tolerance is the ability of a distributed system to continue operating despite disconnected nodes or network partitions.
- How it is used
- Uses partition tolerance to preserve database availability when nodes cannot communicate.
- How deep it goes
- Explains the CAP trade-off, replica responses, consistency levels, and eventual consistency, but defers deeper partition-recovery mechanics.
- Examples
- Illustrates disconnected nodes through a three-replica cluster using ALL, QUORUM, and ONE consistency levels.
- What you can do after
- Evaluate consistency-level choices and operate a replicated ScyllaDB cluster through node-loss trade-offs.
PostgreSQL Mistakes and How to Avoid Them
Partition tolerance is the ability of a distributed system to continue operating despite dropped or delayed network messages.
- How it is used
- Frames PostgreSQL high-availability design as an unavoidable choice among consistency, availability, partition tolerance, and latency.
- How deep it goes
- Defines CAP and PACELC, then demonstrates replication conflicts and schema failure without developing theorem proofs or recovery procedures.
- Examples
- Uses bidirectional PostgreSQL ticket replication, duplicate identity values, and a replicated-column rename that stops the worker.
- What you can do after
- Evaluate/understand distributed-system tradeoffs before selecting PostgreSQL replication and multi-master designs.
Read how PostgreSQL Mistakes and How to Avoid Them explains partition tolerance →
Acing the Frontend Interview
Partition tolerance is the ability of a distributed system to continue operating despite communication failures that divide nodes into unreachable groups.
- How it is used
- Frames distributed-system interview decisions around failures that force consistency and availability trade-offs.
- How deep it goes
- Defines partitions and CAP trade-offs, then contrasts CP and AP systems without detailing partition-recovery internals.
- Examples
- Uses HBase as a CP example, DynamoDB as an AP example, and financial data versus social feeds to contrast consistency needs.
- What you can do after
- Evaluate architectural choices under partitions and justify consistency or availability priorities.
Read how Acing the Frontend Interview explains partition tolerance →
Also covered in
- Grokking Software ArchitectureIn early access (MEAP)
- The Coder CafeIn early access (MEAP)
- Think Distributed Systems
- Machine Learning System Design
What to know first
- distributed systemA distributed system is a computing system whose components run across multiple networked processes or machines and coordinate through communication.
- network partitionA network partition is a failure condition in which disrupted connectivity prevents groups of otherwise operating components in a distributed system from communicating reliably.
- scalabilityScalability is the ability of a system or process to accommodate growth in workload, size, or demand while maintaining acceptable operation.
Related concepts
- CAP theoremused by · The CAP theorem is a distributed-systems impossibility result stating that consistency, availability, and partition tolerance cannot all be guaranteed during a network partition.
- network partitionuses · A network partition is a failure condition in which disrupted connectivity prevents groups of otherwise operating components in a distributed system from communicating reliably.
- partitionaddresses · A division of a whole into distinct parts that together comprise the whole.
- fault tolerancekind of · Fault tolerance is the ability of a system to continue providing correct or acceptable service despite failures in its components or dependencies.
Questions about partition tolerance
What is partition tolerance?
Partition tolerance is the ability of a distributed system to continue operating despite communication failures between parts of the system.
Which Manning books explain partition tolerance?
ScyllaDB in Action, PostgreSQL Mistakes and How to Avoid Them and Acing the Frontend Interview.
What should I know before learning partition tolerance?
Manning books that teach partition tolerance usually introduce distributed system, network partition and scalability first.
What is partition tolerance a kind of?
Partition tolerance is a kind of fault tolerance. Fault tolerance is the ability of a system to continue providing correct or acceptable service despite failures in its components or dependencies.
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.


