kerollmops/raft — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2020-05-05
Build a distributed database where multiple servers agree on the current data state.
Add high-availability replication to an existing service like SQLite (as dqlite does).
Implement a replicated key-value store that survives individual server failures.
Prototype a configuration management system that needs consistent state across machines.
| kerollmops/raft | ac000/find-flv | acc4github/kdenlive-omnifade | |
|---|---|---|---|
| Stars | — | — | 0 |
| Language | C | C | C |
| Last pushed | 2020-05-05 | 2013-04-05 | — |
| Maintenance | Dormant | Dormant | — |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 5/5 | 2/5 | 2/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Requires implementing or wiring a networking and storage interface, a default libuv/Linux AIO implementation is provided to get started faster.
A C library implementing the Raft consensus algorithm, letting multiple servers reliably agree on shared data even when some of them fail or disconnect.
Mainly C. The stack also includes C, libuv, Linux AIO.
Dormant — no commits in 2+ years (last push 2020-05-05).
No license information is stated in the explanation.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.