When is CRDT-based collaboration the wrong choice?
CRDTs add complexity and memory overhead. For purely server-side, single-writer workflows (a spreadsheet with one editor at a time), the cost isn't justified. Also, CRDTs struggle with operations that aren't naturally commutative—like 'set this field to X' without context—requiring careful operation design.
Answered in
CRDTs: Conflict-Free Collaboration at 60fpsEvery user edits a local replica; operations merge automatically into an identical state regardless of arrival order, with no central locking.
Read the full analysisOther questions this article answers
More system design questions
- Why doesn't Google just run Dijkstra faster?
- What is a shortcut edge and when is it precomputed?
- How much space do shortcut edges take compared to the original graph?
- Can Contraction Hierarchies handle dynamic graphs like traffic or road closure?
- Why contract low-degree nodes first instead of high-degree ones?
- What is a CRDT and why does it matter for real-time collaboration?
- How do CRDTs handle concurrent edits without a central server referee?
- Why did Figma move from operational transforms to CRDTs?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design beat.