This is an old revision of the document!


  • Atomicity: All ops happen, or none
  • Consistency: Data will be consistent, no constraints violated
  • Isolation: One transaction cannot read from another non-completed one. If t2 reads write from t1, needs to wait.
  • Durability: Changes have been recorded

“In presence of a network partition, one has to choose between consistency and availability”.

  • Strong consistency
  • Timeline consistency: Typically async master-slave replication.
  • Eventual consistency: Temporarily inconsistent


  • distributed_computing/transactions.1558127947.txt.gz
  • Last modified: 2019/05/17 23:19
  • by phreazer