Sqlite-y-crdt Alternatives

Similar projects and alternatives to sqlite-y-crdt

rqlite

112 14,862 9.9 Go sqlite-y-crdt VS rqlite

The lightweight, distributed relational database built on SQLite.
litefs

38 3,636 8.0 Go sqlite-y-crdt VS litefs

FUSE-based file system for replicating SQLite databases across a cluster of machines
InfluxDB

www.influxdata.com featured

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.
marmot

33 1,628 8.6 Go sqlite-y-crdt VS marmot

A distributed SQLite replicator built on top of NATS
litestack

16 891 9.0 Ruby sqlite-y-crdt VS litestack
sqld

9 917 9.6 Rust sqlite-y-crdt VS sqld

Discontinued LibSQL with extended capabilities like HTTP protocol, replication, and more.
mycelite

8 1,043 5.8 Rust sqlite-y-crdt VS mycelite

Mycelite is a SQLite extension that allows you to synchronize changes from one instance of SQLite to another.
donutdb

4 163 5.3 Go sqlite-y-crdt VS donutdb

Store and query a sqlite db directly backed by DynamoDB.
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better sqlite-y-crdt alternative or higher similarity.

Suggest an alternative to sqlite-y-crdt

sqlite-y-crdt reviews and mentions

Posts with mentions or reviews of sqlite-y-crdt. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-05.

LiteFS Cloud: Distributed SQLite with Managed Backups
9 projects | news.ycombinator.com | 5 Jul 2023

Great that you brought it up. I will fill in the perspective of what I am doing for solving this in Marmot (https://github.com/maxpert/marmot). Today Marmot already records changes via installing triggers to record changes of a table, hence all the offline changes (while Marmot is not running) are never lost. Today when Marmot comes up after a long offline (depending upon max_log_size configuration), it realizes that and tries to catch up changes via restoring a snapshot and then applying rest of logs from NATS (JetStream) change logs. I am working on change that will be publishing those change logs to NATS before it restores snapshots, and once it reapplies those changes after restoring snapshot everyone will have your changes + your DB will be up to date. Now in this case one of the things that bothers people is the fact that if two nodes coming up with conflicting rows the last writer wins.
For that I am also exploring on SQLite-Y-CRDT (https://github.com/maxpert/sqlite-y-crdt) which can help me treat each row as document, and then try to merge them. I personally think CRDT gets harder to reason sometimes, and might not be explainable to an entry level developers. Usually when something is hard to reason and explain, I prefer sticking to simplicity. People IMO will be much more comfortable knowing they can't use auto incrementing IDs for particular tables (because two independent nodes can increment counter to same values) vs here is a magical way to merge that will mess up your data.