Convergence comes from the replicated data type's rules#
CRDTs define state or operations so replicas that receive the relevant updates can converge under the data type's assumptions. Counters, sets, and collaborative sequences can have CRDT designs, each with explicit concurrent-update semantics.
| OT family | CRDT family |
|---|---|
| Transforms operations relative to ordered context | Encodes merge/commutativity rules in replicated state or operations |
| Often coordination-centered | Can accept local updates under its model |
CRDTs do not remove product conflict semantics, tombstone/metadata growth, network cost, authorization, or persistence design. “Conflict-free” refers to convergence properties, not absence of difficult product decisions.
- Adding a CRDT merely because users collaborate.
- Claiming any arbitrary object can merge automatically.
- Ignoring metadata cleanup and offline history.
Related practice problems
Use the manifest-backed prompts below to apply this lesson in a complete design.
Reach this point to mark the lesson as read.