|
You are here |
www.mattritter.me | ||
| | | | |
chelseatroy.com
|
|
| | | | | In December, I took a course in which we attempted to implement the Raft distributed consensus algorithm fromthis paper. Parts 1-5 of this series share insights from the course. From then on, I'm guiding you through my continued work implementing Raft "for fun" (I know. I don't understand me, either). Here's where you can see... | |
| | | | |
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. | |
| | | | |
eli.thegreenplace.net
|
|
| | | | | ||
| | | | |
quickwit.io
|
|
| | | Even after 10 years of programming, I still have a relentless curiosity about new software algorithms, reading papers and blog posts, and learning from other engineers. The best part, however, really comes when you have the opportunity to implement one algorithm and even customize it for your specific use case. In this post, I will walk you through my journey from understanding cluster membership fundamentals to the implementation of Chitchat, our Rust implementation of the Scuttlebutt algorithm with a phi accrual failure detector. | ||