Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

AntidoteDB #419

Open
haadcode opened this issue Dec 7, 2017 · 2 comments
Open

AntidoteDB #419

haadcode opened this issue Dec 7, 2017 · 2 comments
Labels

Comments

@haadcode
Copy link
Member

haadcode commented Dec 7, 2017

AntidoteDB https://syncfree.github.io/antidote and the related discussion on Hacker News https://news.ycombinator.com/item?id=15862895.

This is developed a very strong group of leading experts in CRDTs, including @cmeiklejohn from #40.

This is great work! I love how similar it is to OrbitDB in terms of the underlying data structures and how CRDTs are used, see especially the log.

Correct me if I'm wrong, but afaik this is the only CRDT-only database currently being developed.

@cmeiklejohn
Copy link

cmeiklejohn commented Dec 7, 2017

There's also my work on Lasp, which has an eventually-consistent CRDT-only key-value store embedded inside of it, part of the same SyncFree group. In fact, most of the same CRDTs are supported by both systems.

@bieniusa
Copy link

bieniusa commented Mar 9, 2018

Hey @haadcode !
I was just made aware of your interest in AntidoteDB .
As a unique feature (afaik), AntidoteDB is offering support for transactions (i.e. consistent reads from snapshots and atomic propagation of grouped updates). We are also working on mechanisms for offering optional stronger consistency. The bounded counters are a typical example for that.

If you have any questions, let me know - we would be very happy to see adoption of Antidote.

@daviddias daviddias transferred this issue from ipfs-inactive/research-CRDT Feb 4, 2020
@daviddias daviddias added the CRDTs label Feb 4, 2020
@ipfs ipfs deleted a comment from bitcard Mar 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants