raft
lighthouse
| raft | lighthouse | |
|---|---|---|
| 4 | 124 | |
| 532 | 2,742 | |
| 6.2% | 1.3% | |
| 8.8 | 9.7 | |
| 17 days ago | 2 days ago | |
| Go | Rust | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
raft
-
On Implementation of Distributed Protocols
etcd Raft — a library for maintaining replicated state machines (written in Go);
- Leader election library
-
Implementing a distributed key-value store on top of implementing Raft 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.
-
"In HPA, multiple pods may perform duplicate operations and cause data inconsistency?"
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
lighthouse
-
On Implementation of Distributed Protocols
Lighthouse — an Ethereum consensus client (written in Rust);
- Daily General Discussion - July 5, 2023
- Lighthouse Release v4.3.0
-
Daily General Discussion - May 25, 2023
Daily Goerli: A whole lot more detail on the lighthouse db corruption issue I posted about previously. There's a warning that's been quite frequent on my erigon nodes for a while that doesn't seem to have any impact on its performance. I asked if it should be downgraded to INFO here.
- Lighthouse Release v4.2.0 (Fast Aging Alien)
-
Did I really waited 259 days and missed a 2,29 ethereum block proposal?
According to lighthouse team, the root cause was beacon node waited too long before requesting the payload header. All details here : https://github.com/sigp/lighthouse/issues/4312
- Lighthouse Release v4.1.0 (Uncle Steve)
-
Various validator issues around Shapella
Update LH to 4.0.2-rc.0 More info here https://github.com/sigp/lighthouse/releases/tag/v4.0.2-rc.0
-
Crypto’s Ethereum Network Completes Key Software Upgrade Without a Hitch
Which is not true... full nodes are consuming a lot of CPU now... hot-fix was released, but didn't solve the problem completely: https://github.com/sigp/lighthouse/releases/tag/v4.0.2-rc.0 ... more hot-fixes will be needed
-
Ethereum's pending withdrawals total $1.34 billion after Shapella
https://github.com/sigp/lighthouse 142 contributors
What are some alternatives?
rqlite - The lightweight, distributed relational database built on SQLite.
prysm - Go implementation of Ethereum proof of stake
etcd - Distributed reliable key-value store for the most critical data of a distributed system
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain
Atomix - A Kubernetes toolkit for building distributed applications using cloud native principles
lodestar - 🌟 TypeScript Implementation of Ethereum Consensus
dragonboat - A feature complete and high performance multi-group Raft library in Go.
go-ethereum - Go implementation of the Ethereum protocol
etcd - Distributed reliable key-value store for the most critical data of a distributed system [Moved to: https://github.com/etcd-io/etcd]
Nethermind - A robust execution client for Ethereum node operators.
rawkv - Cloud-native distributed key-value database.
Parity - (deprecated) The fast, light, and robust client for the Ethereum mainnet.