# Strong Consistency

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

**Field:** Software Development  
**Category:** Architecture  
**Also known as:** Strongly Consistent, Linearizability

## Think of it like

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

## 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.

## 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.

## 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.

## Three principles

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

## Related terms

- [Eventual Consistency](https://learn.benibix.com/term/development/eventual-consistency)
- [CAP Theorem](https://learn.benibix.com/term/development/cap-theorem)
- [Atomicity, Consistency, Isolation, Durability (ACID)](https://learn.benibix.com/term/development/acid)
- [Database Replication](https://learn.benibix.com/term/development/database-replication)
- [Distributed System](https://learn.benibix.com/term/development/distributed-system)

## Told apart from

- [Strong Consistency vs Eventual Consistency](https://learn.benibix.com/compare/strong-consistency-vs-eventual-consistency): People think strong and eventual consistency differ only in speed. With strong consistency, every read sees the newest write at once. It does not matter which copy you ask. With eventual consistency, a copy may show old data for a short time, then catch up. Strong is slower, and it may turn calls away when the network splits. Eventual stays fast and up, but you may see an old value.

![Two timelines. In both, a write sets a balance to 150 on the main copy. On the strong timeline, the copies agree first, so a read from any copy straight after shows 150. On the eventual timeline, a read from a second copy straight after still shows the old 100, and only later shows 150.](https://learn.benibix.com/diagrams/dev6-strong-consistency.svg)

---

Source: https://learn.benibix.com/term/development/strong-consistency
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-18
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
