tencent/phxpaxos — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2023-12-04
Build a distributed key-value store where every server ends up with identical data via the Paxos protocol.
Run a configuration server that stays consistent even if some machines crash or the network is delayed.
Build a master-election system that reliably agrees on which server is the active leader.
Wrap an existing single-server service, like an echo service, with PhxPaxos to make it fault-tolerant.
| tencent/phxpaxos | odriverobotics/odrive | nerdlang/nerd | |
|---|---|---|---|
| Stars | 3,370 | 3,614 | 3,616 |
| Language | C++ | C++ | C++ |
| Last pushed | 2023-12-04 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | hard | hard | moderate |
| Complexity | 5/5 | 4/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires writing a custom state machine and integrating the consensus library into your existing service, C++ on Linux only.
A C++ library implementing the Paxos consensus protocol that turns a single-server service into a fault-tolerant distributed system where multiple servers stay in sync, battle-tested in WeChat's production.
Mainly C++. The stack also includes C++, Linux, Paxos.
Dormant — no commits in 2+ years (last push 2023-12-04).
License is not stated in the available content.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.