Skip to content
BENIBIX Learn

Strong Consistency

Development🏗️ ArchitectureDistributed Systems

Also known as Strongly Consistent, Linearizability

Each read shows the last write. It does not matter which copy answers.

Think of it like

It is like one shared board. When someone writes on it, everyone sees the new word.

Example

Emma moves 50 euros between her bank accounts. Her phone and her laptop both show the new balances the moment the transfer is confirmed.

Why it matters

Money, stock counts and bookings cannot show old numbers. Strong consistency stops two people from buying the last seat.

Definition

Strong consistency means that once a write is done, every read after it sees the new value. It does not matter which copy of the data a reader asks. To do this, the copies must agree before the write is confirmed. That takes extra messages, so writes are slower. If the network splits, such a system may turn requests away rather than give old data.
Strong, on top: every copy shows 150 straight away. Eventual, below: one copy lags.

Common mistake

Asking for it everywhere. A like count or a news feed is fine a second late. Eventual consistency is faster and cheaper there.

Key takeaways

  1. 1
    Latest value always. No old reads.
  2. 2
    Copies agree first. Then the write is done.
  3. 3
    It costs speed. Slower, and less often up.

Compare