Skip to Main content Skip to Navigation

Specification of a Transactionally and Causally-Consistent (TCC) database

Abstract : Large-scale application are typically built on top of geo-distributed databases running on multiple datacenters (DCs) situated around the globe. Network failures are unavoidable, but inmost internet services, availability is not negotiable; in this context, the CAP theorem proves that it is impossible to provide both availability and strong consistency at the same time. Sacrificing strong consistency, exposes developers to complex anomalies that are complex to build against.AntidoteDB is a database designed for geo-replication. As it aims to provide high availability with the strongest possible consistency model, it guarantees Transactional Causal Consistency (TCC) and supports CRDTs. TCC means that: (1) if one update happens before another, they will be observed in the same order (causal consistency), and (2) updates in the same transaction are observed all-or-nothing.In AntidoteDB, the database is persisted as a journal of operations. In the current implementation, the journal grows without bound. The main objective of this work is to specify a mechanism for pruning the journal safely, by storing recent checkpoints. This will enable faster reads and crash recovery.
Complete list of metadata

Cited literature [4 references]  Display  Hide  Download
Contributor : Saalik Hatia Connect in order to contact the contributor
Submitted on : Monday, July 20, 2020 - 1:36:22 PM
Last modification on : Thursday, June 9, 2022 - 3:41:06 AM


Files produced by the author(s)


  • HAL Id : hal-02902474, version 2


Saalik Hatia, Marc Shapiro. Specification of a Transactionally and Causally-Consistent (TCC) database. [Research Report] RR-9355, DELYS; LIP6, Sorbonne Université, Inria, Paris, France. 2020. ⟨hal-02902474v2⟩



Record views


Files downloads