strict serializability

The strongest consistency guarantee: all transactions appear to run in a single order that also agrees with real time.

1 articleLast mentioned

Strict serializability is the strongest consistency model for databases and distributed systems. It requires that the outcome of concurrently executed transactions equal that of some sequential execution (serializability) and that this order also respect the real-time order in which the transactions occurred (linearizability). A transaction that begins after another has completed is therefore guaranteed to observe its effects.

It is the easiest model to reason about, but it requires agreement and synchronization among nodes, which raises latency and limits scalability. Distributed databases such as Google Spanner and CockroachDB offer this level of guarantee, while many systems reduce the cost by adopting weaker models such as causal consistency or by providing the guarantee only per key.

This entry is based on AIPOST articles and widely known facts. If something is wrong, please send us a correction request.

Articles covering this entry

  • Pando: The Git Backend OpenAI Built for a 2,442% Surge in CommitsAI News ·

    Pando drops that guarantee in favor of causal consistency, with strict serializability applied only to individual references.

    Read article

Found a mistake or missing an entry?

Wiki entries are based on AIPOST articles and widely known facts. If an entry is wrong, send us a correction request and we will check and fix it. Names from new articles are added to the wiki after the article is published.