/explore
|
You are here 
|
emptysqua.re | ||
| | | | |
decomposition.al
|
|
| | | | | by Devashish Purandare ยท edited by Sohum Banerjea and Lindsey Kuper | |
| | | | |
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... | |
| | | | |
maheshba.bitbucket.io
|
|
| | | | | The road to Paxos is a long one (as with other greek islands) and also somewhat elusive (it's an island, after all). It took me longer than I'd like to admit to obtain a working understanding of the Paxos protocol. In my early attempts, I'd hit a brick wall of complexity: do I really need to know what this particular acceptor is going to do? What's a learner anyway? What does it even mean to decide a value? Why do I need all these ballot numbers? In systems, we deal with complexity via abstraction. For any system, there are three key questions: What abstraction does it implement? What is the design space for such an abstraction? Why is this abstraction useful? In this post, we answer the first two questions for Paxos. This document is not meant to replace th... | |
| | | | |
alexdebrie.com
|
|
| | | In this post, understand the different concepts of consistency as applied to distributed databases, as well as some issues with the conversation of consistency. | ||
