Explore >> Select a destination
|
You are here 
|
jack-vanlightly.com | ||
| | | | |
reubenbond.github.io
|
|
| | | | | ||
| | | | |
www.adamconrad.dev
|
|
| | | | | Ch 5 of my book club review of Designing Data-Intensive Applications by Martin Kleppmann. | |
| | | | |
ketanvijayvargiya.com
|
|
| | | | | Paxos # Paxos is notorious for being difficult to understand. However, the vanilla version seems somewhat straightforward albeit with one limitation: it only allows you to reach consensus on one value. For practical purposes, you want to reach consensus for multiple values in sequence, similar to a replicated log, and you need multi-Paxos for that. And that is hard. Think of basic Paxos as: "do we know already where we'll go for dinner" and, if not, "let's go for burgers". Three roles: proposers, acceptors and learners. Odd number of acceptors. While both proposers and acceptors use numbers in the algorithm, those are just mechanisms to reach consensus on one value. Once consensus is reached, they can continue using more numbers but that value will never cha... | |
| | | | |
shekhargulati.com
|
|
| | | In relational database design one of the key decisions is choosing the right primary key type for tables. In this post I am talking about surrogate or synthetic primary keys. They are called surrogate or synthetic as these keys are not derived from application data. In my experience I have seen very few teams giving... | ||
