Strong Consistency
In plain terms
Guaranteeing all reads see the latest committed write.
Going deeper
Strong consistency ensures every reader immediately sees the most recent data, simplifying reasoning at some cost to availability or latency. There's no stale read.
Under the hood
Often needs coordination/consensus, trading availability under partitions (per CAP); opposite of eventual consistency.
Examples
Bank balances, inventory counts, Spanner, linearizable systems.
Think of it like...
Like a single shared whiteboard everyone sees update the instant it's written.