The name weak consistency can be used in two senses. In the first sense, strict and more popular, weak consistency is one of the consistency models used in the domain of concurrent programming (e.g. in distributed shared memory, distributed transactions etc.).

This article includes a list of references, related reading, or external links, but its sources remain unclear because it lacks inline citations. (May 2017)

A protocol is said to support weak consistency if:

1. All accesses to synchronization variables are seen by all processes (or nodes, processors) in the same order (sequentially) - these are synchronization operations. Accesses to critical sections are seen sequentially.
2. All other accesses may be seen in different order on different processes (or nodes, processors).
3. The set of both read and write operations in between different synchronization operations is the same in each process.

Therefore, there can be no access to a synchronization variable if there are pending write operations. And there can not be any new read/write operation started if the system is performing any synchronization operation.

In the second, more general, sense weak consistency may be applied to any consistency model weaker than sequential consistency.

A stricter condition is strong consistency, where parallel processes can observe only one consistent state.