https://github.com/mprimi/raft-test-suite
Test suite to guide implementations of RAFT consensus protocol
https://github.com/mprimi/raft-test-suite
atomic-broadcast-protocol consensus distributed-systems raft raft-consensus-algorithm
Last synced: about 1 year ago
JSON representation
Test suite to guide implementations of RAFT consensus protocol
- Host: GitHub
- URL: https://github.com/mprimi/raft-test-suite
- Owner: mprimi
- License: apache-2.0
- Created: 2024-02-02T17:59:14.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-12-16T23:58:20.000Z (over 1 year ago)
- Last Synced: 2025-04-16T09:11:04.177Z (about 1 year ago)
- Topics: atomic-broadcast-protocol, consensus, distributed-systems, raft, raft-consensus-algorithm
- Language: Go
- Homepage:
- Size: 238 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# RAFT-protocol-test-suite
## Test suite to guide implementations of RAFT consensus protocol
---
The [RAFT consensus algorithm](https://en.wikipedia.org/wiki/Raft_(algorithm)) was designed to be easier to understand and implement than its older cousin [Paxos](https://en.wikipedia.org/wiki/Paxos_(computer_science)).
While the [paper](https://raft.github.io/raft.pdf) along with plenty of [resources and reference implementations](https://raft.github.io/) can be a great guide, there are still a number of under-specified and ambiguous details that could result in minor and major implementation errors (i.e. deviation from the spec, code bugs, etc.).
Implementing RAFT may be easier than Paxos, but it's still not trivial.
In fact, the well-specified pseudocode may create a false sense of security, leading to implementations that are *confidently wrong*.
This project contains a collection of test specification that cover all the most critical behavior that a RAFT implementation should pass.