raft VS raft

etcd Raft — a library for maintaining replicated state machines (written in Go);

Have you seen this implementation? https://github.com/etcd-io/raft. I’ve used this as a starting point for our consensus with various services.

This is usual in parallel and distributed systems. For k8s, I recommend you either use Apache Zookeeper to coordinate “logical locks” for operations across pods or use the RAFT consensus protocol for scenarios where you need coordination amongst pods. For context, k8s itself uses the RAFT consensus protocol for etcd; see https://github.com/etcd-io/raft

Depending on your exact needs, you could try HashiCorp's Raft implementation: https://github.com/hashicorp/raft

I have found the performance tests very tricky to get to pass without having any input from others. The assignment is really very unforgiving, I would wager the test suite is comparable to how commercial Raft implementations are tested (e.g. https://github.com/hashicorp/raft)

While searching on GitHub, I found a pull request in the Raft implementation by Hashicorp (a distributed consensus algorithm), which we can use to demonstrate the following problem. Let’s start by showing the code (at api.go):

Hey,

you could inspire yourself by hashicorps raft implementation written in go and build one for typescript. Code is quite good to read and Go ins't that far away from typescript.

https://github.com/hashicorp/raft

Production-grade distributed consensus system.

In general Hashicorp's repos are high quality:

https://github.com/hashicorp/raft

Example application: https://github.com/Jille/raft-grpc-example