liveBook · Manning

Quorum

As explained in Grokking Software Architecture

A quorum is a required majority of replicas that must acknowledge an operation before it is considered successful.

A quorum is a majority of replicas acknowledging an update before the database reports success. It sits between the fastest option, which can lose an update if its server crashes, and strict consistency, which waits for every backup server. section 8.2.2

Updating a profile bio

For a profile-bio update, the database waits a few extra milliseconds for a majority of backup servers to confirm receipt. That slows the response slightly but makes the update more reliable. section 8.2.2

How Grokking Software Architecture covers it

How deep it goes
Explains the majority-acknowledgment rule through a profile update, but gives no implementation details.
Examples
Uses a profile-bio update as the middle-ground case between a video Like and a credit-card payment.
What you can do after
Evaluate consistency choices by weighing acknowledgment thresholds against response speed and the risk of losing an update.
How it connects
Links quorum to tunable consistency, eventual consistency, and strict consistency in NoSQL databases.

Also explained in

Compare how 6 books explain quorum →

Related concepts

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