/explore
|
You are here 
|
reubenbond.github.io | ||
| | | | |
maheshba.bitbucket.io
|
|
| | | | | I've heard multiple times that a strong notion of leadership somehow simplifies replication. I don't think this is true. I explain why in this post. | |
| | | | |
maheshba.bitbucket.io
|
|
| | | | | There are three questions to ask of any system: What abstraction does it implement? What is the design space for such an abstraction? Why is this abstraction useful? In a previous post, we examined the Paxos protocol and answered the first two questions. Paxos implements the abstraction of a Write-once Register (a WOR) using a combination of quorums and a two-phase locking protocol. As for the third question: Paxos is useful because it can be used to implement MultiPaxos (among other things). But that's an unhelpful answer unless you know what MultiPaxos does. In this post, we seek to understand MultiPaxos by asking the same three questions of it. To start with, what abstraction does MultiPaxos implement? MultiPaxos implements State Machine Replication. Cons... | |
| | | | |
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. | |
| | | | |
blog.carlosgaldino.com
|
|
| | | Writings on Computer Science and software engineering by Carlos Galdino. | ||
