/explore
|
You are here |
chelseatroy.com | ||
| | | | |
timilearning.com
One common pattern in the previous systems we have discussed like MapReduce, GFS, and VMware FT is that they all rely on a single entity to make the key decisions. While this has the advantage of making it easier for the system to decide, the downside of this approach is that the entity is now a single point of failure. In this post, we'll learn how the Raft consensus algorithm solves this problem. |
|
| | | | | ||
| | | | |
benjamincongdon.me
Learning Raft by making one. |
|
| | | | | ||
| | | | |
briankung.dev
I survived David Beazley's weeklong course on the Raft consensus algorithm that powers technologies like Kubernetes, MongoDB, and Neo4j. Image from https://raft.github.io/ The Raft Consensus Algorithm is a way for a gaggle of computers to agree on a sequence of events, or a "log" of events. Raft is useful for things like databases - once... |
|
| | | | | ||
| | | | |
blogs.eclipse.org
Peter LeVasseur Shares His Insights on the Future of Automotive Software and Fostering Adoption of Open Source Projects |
|
| | | |||