Sequential Consistency

Sequential consistency requires a shared history that preserves each participant’s own operation order. That history does not have to match the real-time order between different participants.

A write may therefore complete before another client’s read starts without forcing that read to observe the write. The model is useful for reasoning about concurrent programs, but applications that rely on immediate cross-client visibility need an additional guarantee.