calm-theorem · also Consistency as Logical Monotonicity

CALM theorem

The CALM theorem connects monotone queries with consistent, coordination-free distributed computation in a relational-transducer model.

Related Observatory article: CALM theorem on hesela.com

Monotonicity: Adding input facts cannot invalidate an output fact already derived. This concerns program results, not increasing timestamps or the monotonic-reads session guarantee. [1]

Execution: The formal model uses connected networks and fair runs: nodes keep taking steps and buffered messages are eventually delivered. Coordination-free does not mean communication-free or that every node immediately knows the complete answer. [2]

Design: Proving reachability from received edges differs from declaring an object unreachable while edges may still arrive. Reclaiming tombstoned data can require later coordination even when foreground updates do not. [1]

Relations

related
CAP theorem, Invariant confluence, Monotonic reads, Eventual consistency

Citations

  1. Hellerstein and Alvaro. Keeping CALM: When Distributed Consistency is Easy. arXiv:1901.01930v2 (2019), sections 1.3-2.2 and 3.4. (accessed 2026-11-10)
  2. Ameloot, Neven and Van den Bussche. Relational transducers for declarative networking. arXiv:1012.2858v1, sections 4-6. (accessed 2026-11-10)
Sources & caveats
  • Source synthesis of the specified formal model and its engineering interpretation; not a runtime performance or fault-tolerance guarantee.

JSON: /data/terms/calm-theorem.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. CALM theorem. Hesela. 2026-11-10. https://hesela.dev/terms/calm-theorem/