# Conflict-free replicated data type

In distributed computing, a conflict-free replicated data type (CRDT) is a data structure which can be replicated across multiple computers in a network, where the replicas can be updated independently and concurrently without coordination between the replicas, and where it is always mathematically possible to resolve inconsistencies which might result.

The CRDT concept was formally defined in 2011 by Marc Shapiro, Nuno Preguiça, Carlos Baquero and Marek Zawirski. Development was initially motivated by collaborative text editing and mobile computing. CRDTs have also been used in online chat systems, online gambling, and in the SoundCloud audio distribution platform. The NoSQL distributed databases Redis and Riak have CRDT data types.[1][2][3][4][5][6][7][8]

## Background

Concurrent updates to multiple replicas of the same data, without coordination between the computers hosting the replicas, can result in inconsistencies between the replicas, which in the general case may not be resolvable. Restoring consistency and data integrity when there are conflicts between updates may require some or all of the updates to be entirely or partially dropped.

Accordingly, much of distributed computing focuses on the problem of how to prevent concurrent updates to replicated data. But another possible approach is optimistic replication, where all concurrent updates are allowed to go through, with inconsistencies possibly created, and the results are merged or "resolved" later. In this approach, consistency between the replicas is eventually re-established via "merges" of differing replicas. While optimistic replication might not work in the general case, it turns out that there is a significant and practically useful class of data structures, CRDTs, where it does work — where it is mathematically always possible to merge or resolve concurrent updates on different replicas of the data structure without conflicts. This makes CRDTs ideal for optimistic replication.

As an example, a one-way Boolean event flag is a trivial CRDT: one bit, with a value of true or false. True means some particular event has occurred at least once. False means the event has not occurred. Once set to true, the flag cannot be set back to false. (An event, having occurred, cannot un-occur.) The resolution method is "true wins": when merging a replica where the flag is true (that replica has observed the event), and another one where the flag is false (that replica hasn't observed the event), the resolved result is true — the event has been observed.

## Types of CRDTs

There are two approaches to CRDTs, both of which can provide strong eventual consistency: operation-based CRDTs[9][10] and state-based CRDTs.[11][12]

The two alternatives are equivalent, as one can emulate the other.[1] Operation-based CRDTs require additional guarantees from the communication middleware;[1] namely that the operations not be dropped or duplicated when transmitted to the other replicas, though they can be delivered in any order. State-based CRDTs also have a disadvantage, which is that the entire state must be transmitted to the other replicas, which may be costly.

### Operation-based CRDTs

Operation-based CRDTs are referred to as commutative replicated data types, or CmRDTs. CmRDT replicas propagate state by transmitting only the update operation. For example, a CmRDT of a single integer might broadcast the operations (+10) or (−20). Replicas receive the updates and apply them locally. The operations are commutative. However, they are not idempotent. The communications infrastructure must therefore ensure that all operations on a replica are delivered to the other replicas, without duplication, but in any order.

Pure operation-based CRDTs[10] are a variant of operation-based CRDTs that reduces the metadata size.

### State-based CRDTs

State-based CRDTs are called convergent replicated data types, or CvRDTs. In contrast to CmRDTs, CvRDTs send their full local state to other replicas, where the states are merged by a function which must be commutative, associative, and idempotent. The merge function provides a join for any pair of replica states, so the set of all states forms a semilattice. The update function must monotonically increase the internal state, according to the same partial order rules as the semilattice.

Delta state CRDTs[12][13] (or simply Delta CRDTs) are optimized state-based CRDTs where only recently applied changes to a state are disseminated instead of the entire state.

### Comparison

While CmRDTs place more requirements on the protocol for transmitting operations between replicas, they use less bandwidth than CvRDTs when the number of transactions is small in comparison to the size of internal state. However, since the CvRDT merge function is associative, merging with the state of some replica yields all previous updates to that replica. Gossip protocols work well for propagating CvRDT state to other replicas while reducing network use and handling topology changes.

Some lower bounds[14] on the storage complexity of state-based CRDTs are known.

## Known CRDTs

### G-Counter (Grow-only Counter)

payload integer[n] P
initial [0,0,...,0]
update increment()
let g = myId()
P[g] := P[g] + 1
query value() : integer v
let v = ${\displaystyle \sum \nolimits _{i}}$ P[i]
compare (X, Y) : boolean b
let b = (${\displaystyle \forall i\in }$ [0, n - 1] : X.P[i] ${\displaystyle \leq }$ Y.P[i])
merge (X, Y) : payload Z
let ${\displaystyle \forall i\in }$ [0, n - 1] : Z.P[i] = max(X.P[i], Y.P[i])


This CvRDT implements a counter for a cluster of n nodes. Each node in the cluster is assigned an ID from 0 to n - 1, which is retrieved with a call to myId(). Thus each node is assigned its own slot in the array P, which it increments locally. Updates are propagated in the background, and merged by taking the max() of every element in P. The compare function is included to illustrate a partial order on the states. The merge function is commutative, associative, and idempotent. The update function monotonically increases the internal state according to the compare function. This is thus a correctly-defined CvRDT and will provide strong eventual consistency. The CmRDT equivalent broadcasts increment operations as they are received.[2]

### PN-Counter (Positive-Negative Counter)

payload integer[n] P, integer[n] N
initial [0,0,...,0], [0,0,...,0]
update increment()
let g = myId()
P[g] := P[g] + 1
update decrement()
let g = myId()
N[g] := N[g] + 1
query value() : integer v
let v = ${\displaystyle \sum \nolimits _{i}}$ P[i] - ${\displaystyle \sum \nolimits _{i}}$ N[i]
compare (X, Y) : boolean b
let b = (${\displaystyle \forall i\in }$ [0, n - 1] : X.P[i] ${\displaystyle \leq }$ Y.P[i] ${\displaystyle \land }$ ${\displaystyle \forall i\in }$ [0, n - 1] : X.N[i] ${\displaystyle \leq }$ Y.N[i])
merge (X, Y) : payload Z
let ${\displaystyle \forall i\in }$ [0, n - 1] : Z.P[i] = max(X.P[i], Y.P[i])
let ${\displaystyle \forall i\in }$ [0, n - 1] : Z.N[i] = max(X.N[i], Y.N[i])


A common strategy in CRDT development is to combine multiple CRDTs to make a more complex CRDT. In this case, two G-Counters are combined to create a data type supporting both increment and decrement operations. The "P" G-Counter counts increments; and the "N" G-Counter counts decrements. The value of the PN-Counter is the value of the P counter minus the value of the N counter. Merge is handled by letting the merged P counter be the merge of the two P G-Counters, and similarly for N counters. Note that the CRDT's internal state must increase monotonically, even though its external state as exposed through query can return to previous values.[2]

### G-Set (Grow-only Set)

payload set A
initial ${\displaystyle \emptyset }$
A := A ${\displaystyle \cup }$ {e}
query lookup(element e) : boolean b
let b = (e ${\displaystyle \in }$ A)
compare (S, T) : boolean b
let b = (S.A ${\displaystyle \subseteq }$ T.A)
merge (S, T) : payload U
let U.A = S.A ${\displaystyle \cup }$ T.A


The G-Set (grow-only set) is a set which only allows adds. An element, once added, cannot be removed. The merger of two G-Sets is their union.[2]

### 2P-Set (Two-Phase Set)

payload set A, set R
initial ${\displaystyle \emptyset }$, ${\displaystyle \emptyset }$
query lookup(element e) : boolean b
let b = (e ${\displaystyle \in }$ A ${\displaystyle \land }$ e ${\displaystyle \notin }$ R)
A := A ${\displaystyle \cup }$ {e}
update remove(element e)
pre lookup(e)
R := R ${\displaystyle \cup }$ {e}
compare (S, T) : boolean b
let b = (S.A ${\displaystyle \subseteq }$ T.A ${\displaystyle \land }$ S.R ${\displaystyle \subseteq }$ T.R)
merge (S, T) : payload U
let U.A = S.A ${\displaystyle \cup }$ T.A
let U.R = S.R ${\displaystyle \cup }$ T.R


Two G-Sets (grow-only sets) are combined to create the 2P-set. With the addition of a remove set (called the "tombstone" set), elements can be added and also removed. Once removed, an element cannot be re-added; that is, once an element e is in the tombstone set, query will never again return True for that element. The 2P-set uses "remove-wins" semantics, so remove(e) takes precedence over add(e).[2]

### LWW-Element-Set (Last-Write-Wins-Element-Set)

LWW-Element-Set is similar to 2P-Set in that it consists of an "add set" and a "remove set", with a timestamp for each element. Elements are added to an LWW-Element-Set by inserting the element into the add set, with a timestamp. Elements are removed from the LWW-Element-Set by being added to the remove set, again with a timestamp. An element is a member of the LWW-Element-Set if it is in the add set, and either not in the remove set, or in the remove set but with an earlier timestamp than the latest timestamp in the add set. Merging two replicas of the LWW-Element-Set consists of taking the union of the add sets and the union of the remove sets. When timestamps are equal, the "bias" of the LWW-Element-Set comes into play. A LWW-Element-Set can be biased towards adds or removals. The advantage of LWW-Element-Set over 2P-Set is that, unlike 2P-Set, LWW-Element-Set allows an element to be reinserted after having been removed.[2]

### OR-Set (Observed-Removed Set)

OR-Set resembles LWW-Element-Set, but using unique tags instead of timestamps. For each element in the set, a list of add-tags and a list of remove-tags are maintained. An element is inserted into the OR-Set by having a new unique tag generated and added to the add-tag list for the element. Elements are removed from the OR-Set by having all the tags in the element's add-tag list added to the element's remove-tag list. To merge two OR-Sets, for each element, let its add-tag list be the union of the two add-tag lists, and likewise for the two remove-tag lists. An element is a member of the set if and only if the add-tag list less the remove-tag list is nonempty.[2]

### Sequence CRDTs

A sequence, list, or ordered set CRDT can be used to build a Collaborative real-time editor, as an alternative to Operational transformation (OT).

Some known Sequence CRDTs are Treedoc,[5] RGA,[15] Woot,[4] Logoot,[16] and LSEQ.[17] CRATE[18] is a decentralized real-time editor built on top of LSEQ and runnable on a network of browsers using WebRTC. LogootSplit [19] was proposed as an extension of Logoot in order to reduce the metadata for sequence CRDTs. MUTE [20] [21] is an online web-based peer-to-peer real-time collaborative editor relying on LogootSplit algorithm.

## Industry use

Redis is a distributed, highly available and scalable in-memory database that uses CRDTs for implementing globally distributed databases based on and fully compatible with Redis open source. SoundCloud open-sourced Roshi, a LWW-element-set CRDT for the SoundCloud stream implemented on top of Redis.[22]

Riak is a distributed NoSQL key-value data store based on CRDTs.[23]. League of Legends uses the Riak CRDT implementation for its in-game chat system, which handles 7.5 million concurrent users and 11,000 messages per second.[24] bet365 (the largest European on-line betting company with 2.5 million simultaneous users peak), stores hundreds of megabytes of data in the Riak implementation of OR-Set.[25]

TomTom employs CRDTs to synchronize navigation data between the devices of a user.[26]

Phoenix, a web framework written in Elixir, uses CRDTs to support real time multi-node information sharing in version 1.2.[27]

Facebook implements CRDTs in their Apollo low-latency "consistency at scale" database.[28]

Teletype for Atom employs CRDTs to enable developers share their workspace with team members and collaborate on code in real time.[29]

Microsoft's Cosmos DB uses CRDT's to enable a multi-master write mode. [30]

Haja Networks' OrbitDB uses operation-based CRDTs in its core data structure, IPFS-Log. [31]

## References

1. ^ a b c Shapiro, Marc; Preguiça, Nuno; Baquero, Carlos; Zawirski, Marek (2011), Conflict-Free Replicated Data Types, Lecture Notes in Computer Science, 6976 (Proc 13th International Symposium, SSS 2011), Grenoble, France: Springer Berlin Heidelberg, pp. 386–400, doi:10.1007/978-3-642-24550-3_29, ISBN 978-3-642-24549-7
2. Shapiro, Marc; Preguiça, Nuno; Baquero, Carlos; Zawirski, Marek (13 January 2011). "A Comprehensive Study of Convergent and Commutative Replicated Data Types". RR-7506. HAL - Inria.
3. ^ Shapiro, Marc; Preguiça, Nuno (2007). "Designing a Commutative Replicated Data Type". Computing Research Repository (CoRR). abs/0710.1784.
4. ^ a b Oster, Gérald; Urso, Pascal; Molli, Pascal; Imine, Abdessamad (2006). "Data consistency for P2P collaborative editing": 259. doi:10.1145/1180875.1180916.
5. ^ a b Letia, Mihai; Preguiça, Nuno; Shapiro, Marc (2009). "CRDTs: Consistency without Concurrency Control". Computing Research Repository (CoRR). abs/0907.0929.
6. ^ Preguiça, Nuno; Marques, Joan Manuel; Shapiro, Marc; Letia, Mihai (June 2009), A Commutative Replicated Data Type for Cooperative Editing, Montreal, Quebec, Canada: IEEE Computer Society, pp. 395–403, doi:10.1109/ICDCS.2009.20, ISBN 978-0-7695-3659-0
7. ^ Baquero, Carlos; Moura, Francisco (1997). "Specification of Convergent Abstract Data Types for Autonomous Mobile Computing". Universidade do Minho.
8. ^ Schneider, Fred (December 1990). "Implementing Fault-Tolerant Services Using the State Machine Approach: A Tutorial".
9. ^ Letia, Mihai; Preguiça, Nuno; Shapiro, Marc (1 April 2010). "Consistency without Concurrency Control in Large, Dynamic Systems". SIGOPS Oper. Syst. Rev. ACM. 44: 29–34. doi:10.1145/1773912.1773921.
10. ^ a b Baquero, Carlos; Almeida, Paulo Sérgio; Shoker, Ali (2014-06-03). Magoutis, Kostas; Pietzuch, Peter, eds. Making Operation-Based CRDTs Operation-Based. Lecture Notes in Computer Science. Springer Berlin Heidelberg. pp. 126–140. doi:10.1007/978-3-662-43352-2_11. ISBN 9783662433515.
11. ^ Baquero, Carlos; Moura, Francisco (1 October 1999). "Using Structural Characteristics for Autonomous Operation". SIGOPS Oper. Syst. Rev. ACM, New York, NY, USA: 90–96.
12. ^ a b Almeida, Paulo Sérgio; Shoker, Ali; Baquero, Carlos (2015-05-13). Bouajjani, Ahmed; Fauconnier, Hugues, eds. Efficient State-Based CRDTs by Delta-Mutation. Lecture Notes in Computer Science. Springer International Publishing. pp. 62–76. doi:10.1007/978-3-319-26850-7_5. ISBN 9783319268491.
13. ^ Almeida, Paulo Sérgio; Shoker, Ali; Baquero, Carlos (2016-03-04). "Delta State Replicated Data Types". arXiv: [cs.DC].
14. ^ Burckhardt, Sebastian; Gotsman, Alexey; Yang, Hongseok; Zawirski, Marek (23 January 2014). "Replicated Data Types: Specification, Verification, Optimality". Int. Symp. on Principles of Prog. Lang. (POPL): 271–284. doi:10.1145/2535838.2535848.
15. ^ Roh, Huyn-Gul; Jeon, Myeongjae; Kim, Jin-Soo; Lee, Joonwon. "Replicated Abstract Data Types: Building Blocks for Collaborative Applications". Jrnl. of Par. and Dist. Comp. 71 (2): 354–368. doi:10.1016/j.jpdc.2010.12.006.
16. ^ Weiss, Stephane; Urso, Pascal; Molli, Pascal (2010). "Logoot-Undo: Distributed Collaborative Editing System on P2P Networks". IEEE Transactions on Parallel and Distributed Systems. 21 (8): 1162–1174. doi:10.1109/TPDS.2009.173. ISSN 1045-9219.
17. ^ Nédelec, Brice; Molli, Pascal; Mostefaoui, Achour; Desmontils, Emmanuel (2013). "LSEQ an adaptive structure for sequences in distributed collaborative editing": 37. doi:10.1145/2494266.2494278.
18. ^ Nédelec, Brice; Molli, Pascal; Mostefaoui, Achour (2016). "CRATE: Writing Stories Together with our Browsers". Proceedings of the 25th International Conference Companion on World Wide Web. p. 231. doi:10.1145/2872518.2890539.>
19. ^ André, Luc; Martin, Stéphane; Oster, Gérald; Ignat, Claudia-Lavinia (2013). "Supporting Adaptable Granularity of Changes for Massive-scale Collaborative Editing". Proceedings of the International Conference on Collaborative Computing: Networking, Applications and Worksharing – CollaborateCom 2013. pp. 50–59. doi:10.4108/icst.collaboratecom.2013.254123.>
20. ^ "MUTE". Coast Team. March 24, 2016.
21. ^ Nicolas, Matthieu; Elvinger, Victorien; Oster, Gérald; Ignat, Claudia-Lavinia; Charoy, François (2017). "MUTE: A Peer-to-Peer Web-based Real-time Collaborative Editor". Proceedings of ECSCW Panels, Demos and Posters 2017. doi:10.18420/ecscw2017_p5.>
22. ^ Bourgon, Peter (9 May 2014). "Roshi: a CRDT system for timestamped events". SoundCloud.
23. ^ "Introducing Riak 2.0: Data Types, Strong Consistency, Full-Text Search, and Much More". Basho Technologies, Inc. 29 October 2013.
24. ^ Hoff, Todd (13 October 2014). "How League of Legends Scaled Chat to 70 Million Players - It Takes Lots of Minions". High Scalability.
25. ^ Macklin, Dan. "bet365: Why bet365 chose Riak". Basho.
26. ^ Ivanov, Dmitry. "Practical Demystification of CRDTs".
27. ^ McCord, Chris. "What makes Phoenix Presence Special".
28. ^ Mak, Sander. "Facebook Announces Apollo at QCon NY 2014".
29. ^ "Code together in real time with Teletype for Atom". Atom.io. November 15, 2017.
30. ^ rimman. "Multi-master at global scale with Azure Cosmos DB". docs.microsoft.com. Retrieved 2018-05-07.
31. ^ "OrbitDB/ipfs-log on Github". Retrieved 2018-09-07.