overlord VS bft-json-crdt

Compare overlord vs bft-json-crdt and see what are their differences.

bft-json-crdt

🏰 the first JSON-like Byzantine Fault Tolerant CRDT (by jackyzha0)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
overlord bft-json-crdt
1 2
78 188
- -
0.0 10.0
8 months ago over 1 year ago
Rust Rust
MIT License MIT License
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.

overlord

Posts with mentions or reviews of overlord. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-01.
  • Muta is part of Nervos?
    3 projects | /r/NervosNetwork | 1 Nov 2021
    Muta is chain framework (e.g. substrate or cosmos-sdk) being intensively worked on in 2020. The design goal of Muta is high performance and usability. Muta can process ~3k transactions per second and achieve instant finality thanks to a BFT consensus implementation named Overlord.

bft-json-crdt

Posts with mentions or reviews of bft-json-crdt. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-11-21.
  • Building a BFT JSON CRDT
    4 projects | news.ycombinator.com | 21 Nov 2022
    I'm quite surprised by the [benchmarks versus Automerge JS & Rust](https://github.com/jackyzha0/bft-json-crdt#benchmarks) when it comes to memory:

    > Ours (Basic) 27.6MB

    > Ours (BFT) 59.5MB

    > Automerge (Rust) 232.5MB

    I would expect adding the public key tracking to use more memory; I wonder how Automerge is spending so much more memory. Possibly on a bunch of internal caches or memoization that give the order-of-magnitude improvement in speed?

    > Ops: 100k

    > Ours (Basic) 9.321s

    > Ours (BFT) 38.842s

    > Automerge (Rust) 0.597s

What are some alternatives?

When comparing overlord and bft-json-crdt you can also consider the following projects:

paxakos - Rust implementation of Paxos consensus algorithm

y-sweet - A standalone yjs server with persistence to S3 or filesystem.

tikv - Distributed transactional key-value database, originally created to complement TiDB

diamond-types - The world's fastest CRDT. WIP.

muta - Muta is a high-performance blockchain framework.

cr-sqlite - Convergent, Replicated SQLite. Multi-writer and CRDT support for SQLite

cita - A high performance blockchain kernel for enterprise users.

AlephBFT - Rust implementation of Aleph consensus protocol

prolly-trees - Hash consistent search trees.