mono

FYI, Zero uses incremental view maintenance internally as the core of its sync engine: https://zero.rocicorp.dev/docs/introduction IVM is what allows the core feature of our DX: that users can just do a fairly large query with sorts and joins, like: zero.query.posts.where('authorID', 42) .orderBy('created', 'desc') .limit(1000) .related('comments', c => c.orderBy('created', 'desc').limit(10)) ... and we sync updates to this query incrementally to the client. TanStack DB also uses IVM, but only client-side currently. If you are interested in such things, you can take a poke around the source here: https://github.com/rocicorp/mono/tree/main/packages/zql. Or come find us in Discord: https://discord.rocicorp.dev/

No. When we started the project we used prolly trees initially, but we don't need the content addressing feature for Zero and all the hashing was quite expensive. So now we just use a plain immutable b-tree: https://github.com/rocicorp/mono/tree/main/packages/replicac...

> - Zero Sync: https://github.com/rocicorp/mono Doesn't even have a readme :D Raise the bar a bit maybe.

Honourable mentions of some more excellent fully open-source sync engines: - Zero Sync: https://github.com/rocicorp/mono - Triplit: https://github.com/aspen-cloud/triplit