CRDTs Illustrated
summary
Explains concrete rules and limits: operation-based vs state-based CRDTs with three operation-based requirements (concurrent ops must commute, idempotent delivery, per-source ordering) and the state-based requirements (monotonic merge that is commutative and associative). Shows real implementations—Riak 2 Data Types and a browser demo using swarm.js—and demonstrates offline clients continue working and converge when the server returns, plus patterns to build counters and sets with tombstones or version vectors.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:33The Problem
- 4:00Consistency
- 8:42Exactly once delivery
- 10:34Sets
- 15:58Statebased utilities
- 17:19Concurrent operations
- 18:30Order delivery
- 20:06Combine
- 21:13Version Factors
- 22:11StateBased Unities
- 23:47Recap
- 24:23Demos
- 29:46Conclusion
- 30:58Further material
- 31:46Questions
related talks
29mCRDT: Conflict-free Data Types for Collaborative Editing and Offline-First
33mConvergent/Divergent
34mUsing CRDTs Beyond Text Editors
36mCRDT Architecture and Group Systems
45mBuild better apps using CRDTs
49mWhat CRDTs, distributed editing and the speed of light means to your writer friends
32mCRDT and other new ideas for client-server communication
13mHow to make a real-time collaborative text editor in 5 easy steps!