CRDT Benchmarks

What’s the future of this work? Is it planned to be entirely standalone? Planning to build integration with popular editors? Planning a websocket server implementation with hooks etc / a hosted solution?

Re: CRDT Benchmarks

#5

Post by MrOwnPut » Mon, May 22, 2023, 5:14 PM UTC

That's crazy. But the main draw of Y.JS is how easy it is to use.

It has many providers, easy persistence, and many integrations.

Maybe make a compatibility layer to use the Y.JS ecosystem?

Re: CRDT Benchmarks

#6

Post by johncalvinyoung » Mon, May 22, 2023, 5:22 PM UTC

Very interested in seeing progress, JSON CRDTs benchmarked with JS objects and arrays, I currently have an implementation based on Automerge but it's borderline nonviable on our largest data structures.

Re: CRDT Benchmarks

#7

Post by simonw » Mon, May 22, 2023, 5:34 PM UTC

I'm still hoping for a CRDT implementation with robust, thoroughly tested libraries for both Python and JavaScript that can talk to each other - I want to run Python on the server and JavaScript in the client and keep the two in sync with each other.

Closest I've seen to that is automerge but the Python version doesn't appear to be actively maintained or packaged for PyPI yet: https://github.com/automerge/automerge-py

UPDATE: It looks like this might be what I'm after: https://github.com/y-crdt/ypy

Re: CRDT Benchmarks

#8

Post by fnordsensei » Mon, May 22, 2023, 6:31 PM UTC

I think the idea of the Rust implementations of Y and A is portability, primarily. A JS implementation alone is very opinionated about, for example, what your backend should look like. A Rust ditto will be less opinionated and more accessible in a variety of environments.

I don’t think the main point is the supposed superiority of WASM vs JS in terms of performance, as the article surmises.

Re: CRDT Benchmarks

#9

Post by syncerr » Mon, May 22, 2023, 6:45 PM UTC

The death stroke for these types of projects seems to be lack of funding. This project is sponsored by nlnet[0] providing between 5k - 50k EU per year. Let's hope this gets additional resources.

As a note, it appears to use Elastic's 2.0 license preventing selling software that includes this library [1]

[0] https://nlnet.nl/project/JSON-Joy/

[1] https://github.com/streamich/json-joy/blob/master/LICENSE

Re: CRDT Benchmarks

#10

Post by samwillis » Mon, May 22, 2023, 7:06 PM UTC

I need to dig into this more, but I'm sceptical of only benchmarking ops/second, that's not really a problem that needs solving, the existing toolkits are fast enough. Also, this benchmark doesn't show document size and growth, that is something where more research is needed.

Always excited for any CRDT innovations though, and I'm sure there is stuff to learn from this work.