To OT or CRDT, That Is the Question

rw-book-cover

Metadata

Highlights

  • When it comes to more advanced structures such as rich text editing, the crux of the problem with CRDTs is user intent. Working at such a low level provides an easier guarantee of eventual consistency, but you lose sight of the big picture. For example in OT we can define a “split text node” operation which can be complicated to transform but is very well understood to have certain properties in a rich text editor. Whereas in CRDT, the changes are more data-focussed and it becomes very clinical. A good example is splitting a text node. Think about what that might take at the data level: (View Highlight)

title: “To OT or CRDT, that is the question” author: “Andrew Herron” url: ”https://www.tiny.cloud/blog/real-time-collaboration-ot-vs-crdt/” date: 2023-07-29 source: reader tags: media/articles

To OT or CRDT, that is the question

rw-book-cover

Metadata

Highlights

  • When it comes to more advanced structures such as rich text editing, the crux of the problem with CRDTs is user intent. Working at such a low level provides an easier guarantee of eventual consistency, but you lose sight of the big picture. For example in OT we can define a “split text node” operation which can be complicated to transform but is very well understood to have certain properties in a rich text editor. Whereas in CRDT, the changes are more data-focussed and it becomes very clinical. A good example is splitting a text node. Think about what that might take at the data level: (View Highlight)

title: “To OT or CRDT, That Is the Question” author: “Andrew Herron” url: ”https://www.tiny.cloud/blog/real-time-collaboration-ot-vs-crdt/” date: 2023-12-19 source: reader tags: media/articles

To OT or CRDT, That Is the Question

rw-book-cover

Metadata

Highlights

  • When it comes to more advanced structures such as rich text editing, the crux of the problem with CRDTs is user intent. Working at such a low level provides an easier guarantee of eventual consistency, but you lose sight of the big picture. For example in OT we can define a “split text node” operation which can be complicated to transform but is very well understood to have certain properties in a rich text editor. Whereas in CRDT, the changes are more data-focussed and it becomes very clinical. A good example is splitting a text node. Think about what that might take at the data level: (View Highlight)