opacity · research · also Transactional opacity

Opacity

Opacity is a transaction-correctness condition requiring committed, aborted and unfinished transactions to observe states consistent with a legal sequential execution that preserves transaction real-time order.

Scope: A transaction can observe its own writes and earlier committed effects in the sequential explanation; another transaction's aborted writes do not become shared state. Checking only committed transactions misses this obligation. [1]

Prefixes: The modern formulation requires every execution prefix to admit a suitable sequential explanation, with pending operations handled by completion rules. This explicit prefix condition is stated in Bila et al. Definition 4; the original 2008 paper discusses prefix closure separately in section 5.2. [2] [1]

Application: Beldi targets opacity for its transactional workflows, with locking and distributed commit. Nontransactional access that bypasses those locks is outside that guarantee. [3]

Constructed example: Initially x = y = 0. One transaction atomically commits x = y = 1. A concurrent read-only transaction sees x = 0, then y = 1, and aborts. The writer alone has a serial committed history, but neither ordering of both transactions explains the reader's values. Aborting does not erase that observation. This illustrates the criterion, not an observed Beldi execution. [1] [2]

Relations

related
Beldi, Strict serializability

Limitations

  • Opacity is a safety condition, not a guarantee that a transaction eventually commits. [1]
  • Ordinary opacity does not by itself specify crash recovery or persistent storage; durable opacity adds a crash-aware contract. [2]

Citations

  1. Rachid Guerraoui and Michal Kapalka. On the Correctness of Transactional Memory. PPoPP 2008, sections 4, 5.1-5.2 and 7. (accessed 2026-11-16)
  2. Bila et al. Defining and Verifying Durable Opacity: Correctness for Persistent Software Transactional Memory. arXiv:2004.08200v1, Definitions 4-5. (accessed 2026-11-16)
  3. Zhang et al. Fault-tolerant and transactional stateful serverless workflows. OSDI 2020, section 6.2. (accessed 2026-11-16)
Sources & caveats
  • Primary-source synthesis, not an implementation test, proof or benchmark.

JSON: /data/terms/opacity.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Opacity. Hesela. 2026-11-16. https://hesela.dev/terms/opacity/