crdt - Interjected Future

crdt

A collection of 5 posts

A simple way to understand CRDTs

A simple way to understand CRDTs

🔰If CRDTs (Conflict-free Replicated Data Types) are new to you, check out this previous post. There's a simple way to understand CRDTs: It leverages algebra to unmix the inevitable mixing of data when syncing over an unreliable network. Why are networks unreliable? For one, it'd be really expensive to build

CRDTs Turned Inside Out

CRDTs Turned Inside Out

🔰If CRDTs are new to you, here are some introductory links. - An interactive intro to CRDTs [https://jakelazaroff.com/words/an-interactive-intro-to-crdts/] - An introduction to state-based CRDTs [https://www.bartoszsypytkowski.com/the-state-of-a-state-based-crdts/] - CRDTs for non-academics [https://www.youtube.com/watch?v=vBU70EjwGfw] - CRDT: The Hard Parts [https:

Trade-offs between Different CRDTs

Trade-offs between Different CRDTs

🔰If CRDTs are new to you, here are some introductory links. - An interactive intro to CRDTs - An introduction to state-based CRDTs - CRDTs for non-academics - CRDT: The Hard Parts - Readings in CRDTs - crdt.tech What are the trade-offs between different kinds of CRDTs (Conflict-free Replicated

Lab Notes #024 Merkle DAGs and retrofitting into relational

Lab Notes #024 Merkle DAGs and retrofitting into relational

I been reading various papers on CRDTs to deepen my understanding of them. That's when I happened upon a paper that constructed Merkle-CRDTs from Merkle-DAGs [https://arxiv.org/pdf/2004.00107.pdf]. > Surprisingly, the internal merkle data structure of Git is like a vector clock. It establishes causal order of

Lab notes #021 CRDTs in depth and AI explaining code

Lab notes #021 CRDTs in depth and AI explaining code

In the course of building the demo todo list local-first app, I've found that different CRDT libraries have different assumptions about the data access pattern you're using. Automerge [https://github.com/automerge/automerge] and Yjs [https://github.com/yjs/yjs] prioritize text editing, but Automerge assumes a JSON interaction whereas