bft-json-crdt VS wiki-collab

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

bft-json-crdt

🏰 the first JSON-like Byzantine Fault Tolerant CRDT (by jackyzha0)
Bft CRDT crdt-implementations JSON json-crdt
Source Code
Suggest alternative
Edit details

wiki-collab

A Hyper Hyper Space datatype for a collaborative, moderated wiki (by hyperhyperspace)
Suggest topics
Source Code
Suggest alternative
Edit details
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
bft-json-crdt wiki-collab
2 1
188 1
- -
10.0 0.0
over 1 year ago about 1 year ago
Rust TypeScript
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.

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

wiki-collab

Posts with mentions or reviews of wiki-collab. 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
    This is a cool idea, but I didn't find any examples of max length constraints or other normalization rules in the source code I reviewed. Maybe there's something in there.

    Here's some source code for an early, work-in-progress Wiki CRDT: https://github.com/hyperhyperspace/wiki-collab/blob/master/s...

    Page in the Wiki. Note that data types have a validate method that returns true or false; maybe if false, they're just dropped from the UI? Not sure how the method is used. https://github.com/hyperhyperspace/wiki-collab/blob/master/s...

    I haven't found the underlying text or rich text CRDT implementation yet.

What are some alternatives?

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

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

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

overlord - Overlord consensus protocol.

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

AlephBFT - Rust implementation of Aleph consensus protocol

prolly-trees - Hash consistent search trees.

bft-json-crdt vs y-sweet bft-json-crdt vs diamond-types bft-json-crdt vs overlord bft-json-crdt vs cr-sqlite bft-json-crdt vs AlephBFT bft-json-crdt vs prolly-trees