An industrial-grade C++ implementation of RAFT consensus algorithm based on brpc, widely used inside Baidu to build highly-available distributed systems.
-
Updated
Feb 25, 2022 - C++
{{ message }}
An industrial-grade C++ implementation of RAFT consensus algorithm based on brpc, widely used inside Baidu to build highly-available distributed systems.
A list of papers about distributed consensus.
VI Worsened, a lightweight and fun VI clone.
Bamboo is a prototyping and evaluation framework that studies the next generation BFT (Byzantine fault-tolerant) protocols specific for blockchains, namely chained-BFT, or cBFT.
Rabia: Simplifying State-Machine Replication Through Randomization (SOSP 2021)
Golang based implementation of the Generic Multicast protocol.
An implementation of a self-stabilizing replicated state machine based on failure detectors.
[WIP] Stellar Consensus Protocol implementation
Implementation of a simple and high-performant distributed ledger technologies platform, VOIDChain, based on a popular Byzantine Fault-Tolerant state machine replication Java library BFT-SMaRt.
A scalable and lightweight REST API service that clients or external services can use to communicate with the VOIDChain platform.
jRCM, the Java RDMA Communications Manager, is a library that aims to make building RPCs with RDMA for SMR systems in Java easy. It was developed for a MSc CS Thesis Project : "Efficient State Machine Replication With RDMA RPCs in Java". jRCM was used in a forked Hazelcast repository, to conduct the research for the Thesis.
Algorithms and Distributed Systems Project 2 - Replicated Service using State Machine Replication.
Add a description, image, and links to the state-machine-replication topic page so that developers can more easily learn about it.
To associate your repository with the state-machine-replication topic, visit your repo's landing page and select "manage topics."
Even though this is just a sample application, this kind of error detection might help avoid surprising results if there is a simple typo in configuration. Maybe address in a separate issue? The same also applies to
sample/configpackage.Originally posted by @sergefdrv in hyperledger-labs/minbft#134