-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
12 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,13 @@ | ||
# RAFT-protocol-test-suite | ||
Test suite to guide implementations of RAFT consensus protocol | ||
## 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. |