- eventually-consistent-mesh VS electric_dart
- eventually-consistent-mesh VS fugue-bench
- eventually-consistent-mesh VS pg_crdt
- eventually-consistent-mesh VS multiversion-concurrency-contro
- eventually-consistent-mesh VS crdt-benchmarks
- eventually-consistent-mesh VS text-diff
- eventually-consistent-mesh VS yjs-sqlite-test
- eventually-consistent-mesh VS yjs-pg-test
Eventually-consistent-mesh Alternatives
Similar projects and alternatives to eventually-consistent-mesh
-
electric
Local-first sync layer for web and mobile apps. Build reactive, realtime, local-first apps directly on Postgres.
-
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.
-
multiversion-concurrency-control
Implementation of multiversion concurrency control, Raft, Left Right concurrency Hashmaps and a multi consumer multi producer Ringbuffer, concurrent and parallel load-balanced loops, parallel actors implementation in Main.java, Actor2.java and a parallel interpreter
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
crdt-benchmarks
Discontinued Real world text editing traces for benchmarking CRDT and Rope data structures [Moved to: https://github.com/josephg/editing-traces] (by josephg)
-
hash-db
Experimental distributed pseudomultimodel keyvalue database (it uses python dictionaries) imitating dynamodb querying with join only SQL support, distributed joins and simple Cypher graph support and document storage
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
eventually-consistent-mesh reviews and mentions
-
The growing pains of database architecture
https://github.com/samsquire/eventually-consistent-mesh/blob...
I wrote a Jepsen test that because it is not linerarizable, it fails.
My script abandons the C(onsistency) of CAP and maintains (A)vailability and (P)artition tolerance. It assumes the network shall heal and the replication shall resume. In PACELC theory in During normal operation it prefers Availability during Partitions and Else Latency in normal operations.
How do you build a system around a database where values can no longer be valid at any time? If I kick off a process in the database with a value that was only reported by one replica that was partitioned away from the majority of the network, what do I do?
My immediate thoughts are to create dependency relationships to values that are on the agreed path, data that is based on a failed branch is not valid.
https://github.com/samsquire/eventually-consistent-mesh
-
CRDT-richtext: Rust implementation of Peritext and Fugue
https://github.com/samsquire/eventually-consistent-mesh
I implemented an barebones toy SQL and Graph cypher and document storage database
Stats
The primary programming language of eventually-consistent-mesh is Python.
Popular Comparisons
Sponsored