Skip to content(if available)orjump to list(if available)

CRDT and SQLite: Local-First Value Synchronization

CRDT and SQLite: Local-First Value Synchronization

7 comments

·October 9, 2025
Visit

philsnow

We shouldn't be surprised because the writer works with both sqlite and AI but

> Here’s a polished section you can insert into your article (it fits naturally after the Sync Phase section):

withinboredom

This works assuming everyone has the same clock or performs changes causually distant from each other. It fails to work if, say, 1000 people all make a change around the same time. This also applies to lamport timestamps.

p1necone

If a thousand people all made a change at the same time in a totally deterministic, always online system a single one of those writes would arbitrarily win in exactly the same way.

In practice "1000 people edit same thing at same time" is not a problem that needs to be solved via software, the users are just doing silly things and getting silly results.

withinboredom

If it isn’t handled correctly, you’ll eventually end up with parallel histories on different devices. Even if it isn’t 1000 people, people will share documents with entire classrooms, offices, etc., which increases the probability of this situation tremendously.

marcobambini

The algorithm has a way to resolve conflicts even if, by any chance, the Lamport clock has the same value in all peers

withinboredom

Yeah, but the fact that they didn’t even mention it in their post is why I brought it up.

briandw

For a primer on CRDTs, Martin Kleppmann has a number of good videos: https://www.youtube.com/watch?v=x7drE24geUw