automerge VS dotted-logootsplit

Compare automerge vs dotted-logootsplit and see what are their differences.

automerge

A JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically. (by automerge)
Our great sponsors
  • Scout APM - A developer's best friend. Try free for 14-days
  • Nanos - Run Linux Software Faster and Safer than Linux with Unikernels
  • SaaSHub - Software Alternatives and Reviews
automerge dotted-logootsplit
10 1
11,548 27
1.7% -
9.4 0.0
14 days ago 4 months ago
JavaScript TypeScript
MIT License Mozilla Public License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

automerge

Posts with mentions or reviews of automerge. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-02.

dotted-logootsplit

Posts with mentions or reviews of dotted-logootsplit. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-07-31.
  • 5000x Faster CRDTs: An Adventure in Optimization
    8 projects | news.ycombinator.com | 31 Jul 2021
    Yes, xray was abandoned and teletype is written in JS.

    I understand your point and as a researcher and engineer I know your feeling. I took some cautions by using "Some optimizations". I value engineering as much as research and I'm bothered when I heard any side telling the other side that their work is worthless. Your work and the work of Kevin Jahns are very valuable and could improve the way that researchers and engineers do benchmarks.

    This is still hard for me to determine when position-based list CRDT (Logoot, LogootSPlit, ...) are better than tombstone-based list CRDT (RGA, RgaSplit, Yata, ...). It could be worth to assess that.

    3 year ago I started an update of LogootSplit. The new CRDT is named Dotted LogootSplit [1] and enables delta-synchronizations. The work is not finished: I had other priorities such as writing my thesis... I have to perform some benchmark. However I'm more interested in the hypothetical advantages of Dotted LogootSplit regarding synchronization over unreliable networks. From an engineering point-of-view, I'm using a partially-persistent-capable AVL tree [2]. Eventually I would like to switch to a partially-persistent-capable b-tree. Unfortunately writing a paper is very time consuming, and time is missing.

    I still stick with JS/TS because in my viewpoint Wasm is not mature yet. Ideally, I would like to use a language that compiles both to JS and Wasm. Several years ago I welcomed Rust with a lot of enthusiasm. Now I'm doubtful about Rust due to the inherent complexity of the language.

    [1] https://github.com/coast-team/dotted-logootsplit/tree/dev

What are some alternatives?

When comparing automerge and dotted-logootsplit you can also consider the following projects:

teletype-crdt - String-wise sequence CRDT powering peer-to-peer collaborative editing in Teletype for Atom.

crdt-benchmarks - A collection of CRDT benchmarks

yjs - Shared data types for building collaborative software

earthstar - A distributed, syncable document database for making p2p apps