crdt-benchmarks VS yjs-sqlite-test

Diamond types author here! Congratulations on getting your crdt working! It’s lovely to see a new generation of CRDTs which have decent performance.

And nice stuff implementing peritext! I’d love to do the same in diamond types at some point. You beat me to it!

Im building a little repository of real world collaborative editing traces to use when benchmarking, comparing and optimising text based CRDTs[1]. The automerge-perf editing trace isn’t enough on its own. And we’re increasingly converging on a format for multi user concurrent editing traces too[2]. It’d be great to add some rich text editing traces in the mix if you’re interested in recording something, so we can also compare how peritext performs in different systems.

Anyway, welcome to the community! Love to have more implementations around!

https://github.com/josephg/crdt-benchmarks

https://github.com/dmonad/crdt-benchmarks/issues/20

I have a few more real world editing traces that I use for jumprope in this repository: https://github.com/josephg/crdt-benchmarks

I agree that full stack support is the missing pice that's need to make use explode. But I do think the current implementations will get there.

CRDTs are fairly unique in that you need them to be exposed very close to the front of your stack in order to capture user intent, but you also need support further back in your stack for merging, replication, and querying.

We have good front end support and there are multiple exciting projects building collaboration servers for them. What I think is missing is support in database, that's what I've been experimenting with (below). If you are building an offline enabled app, having the ability to generate diffs and merge in database enables easy multi document sync.

Also most general purpose CRDTs are a combination of JSON and XML like data structures, it's useful to be able to query the structures in your database. For example if you build a notes app that supports inline tags, if useful to be able to query and index those from within the XML like structure without having to dump the whole thing out at another layer of your stack.

Yjs Postgres: https://github.com/samwillis/yjs-pg-test

Yjs SQLite: https://github.com/samwillis/yjs-sqlite-test

(These are just early experiments, I'm working on a cleaner shared implementation with support for various SQLite bindings, and better querying)

Day job (contract): Massive overhaul of an antibody workbench for drug discovery.

Evenings: Building out a concept for a "YSQL" bringing CRDTs (Yjs) to SQLite and Postgres. CRDTs are great for real-time, but also awesome for offline for async collaboration. Using the same CRDT for both front end data structures and backend database merging seems to me to be a good combination. The plan is to build out some simple primitives first, then layer a SQLite (WASM in browser) <-> Postgres sync system on top for local copying and modification of datasets.

Proof of concepts:

https://github.com/samwillis/yjs-sqlite-test

https://github.com/samwillis/yjs-pg-test