|
You are here |
emptysqua.re | ||
| | | | |
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... | |
| | | | |
benjamincongdon.me
|
|
| | | | | Learning Raft by making one. | |
| | | | |
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. | |
| | | | |
nurkiewicz.com
|
|
| | | Clocks are important to computers. Computers need to order events in a way understandable to humans. Every computer has a bunch of internal counters, like CPU ticks. But they only work within one machine. We need a way to have a reliable, global clock, that is synchronized between many computers. Why, exactly? Well, imagine you are selling tickets to The Rolling Stones concert. They sometimes sell within a few seconds. First come, first served. But who was first, if selling happens asynchronously in mult... | ||