|
You are here |
decomposition.al | ||
| | | | |
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... | |
| | | | |
blog.willportnoy.com
|
|
| | | | | My group at Microsoft uses Azure for many of its projects. We have a shared data store that we run as a service in Azure, and some of the g... | |
| | | | |
eli.thegreenplace.net
|
|
| | | | | [AI summary] An introductory post from a blog series detailing the implementation of the Raft distributed consensus algorithm in the Go programming language. | |
| | | | |
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. | ||