Explore >> Select a destination
|
You are here 
|
benjamincongdon.me | ||
| | | | |
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. | |
| | | | |
eli.thegreenplace.net
|
|
| | | | | ||
| | | | |
jack-vanlightly.com
|
|
| | | This post continues my series looking at log replication protocols, within the context of state-machine replication (SMR) or just when the log itself is the product (such as Kafka). So far I've been looking at Virtual Consensus, but now I'm going to widen the view to look at how log replication protocols can be disaggregated in general (there are many ways). In the next post, I'll do a survey of log replication systems in terms of the types of disaggregation described in this post. | ||
