A leaderless distributed cache/database
-
Updated
Nov 11, 2026 - Go
A leaderless distributed cache/database
Dynamo-inspired distributed leader-less key-value database that has no unique features and no apparent reason to exist
In a nutshell, EinsteinDB is a persistent indexing scheme based off of LSH-KVX that exploits the distinct merits of hash index and B+-Tree index to support range scan and avoids long NVM writes for maintaining consistency; thus improving on LSH’s performance guarantees for skewed data and adopts ordered-write consistency to ensure crash consiste…
Distributed cron and interval scheduling with no leader and no distributed locks. One atomic claim selects one instance per scheduled run.
Cloud-native geo-distributed leaderless message broker
Leaderless AP key-value store in Go: CRDT conflict resolution, no quorums, Merkle anti-entropy, gossip membership
Drone airspace deconfliction (ASTM F3548 DSS rule) on three equal instances across three continents, no leader — measurements and recording
Open challenge: choose the arrival order for 3,000 transactions. The ledger hash comes out the same.
A festival with no payment server: registers that die at peak, and selling through a network split without double spending. Measurements, raw data, verify scripts.
Vortex DSE: leaderless distributed systems. Correctness checked with TLA+/TLAPS.
Three Teslas, one ledger, no server — Tesla fleet-telemetry records agreed among the cars themselves (Vortex device mode), next to Tesla's own reference server
To associate your repository with the leaderless topic, visit your repo's landing page and select "manage topics."