Explore >> Select a destination
|
You are here 
|
loonytek.com | ||
| | | | |
tomaugspurger.net
|
|
| | | | | Last week, I was fortunate to attend Dave Beazley's Rafting Trip course. The pretext of the course is to implement the Raft Consensus Algorithm. I'll post more about Raft, and the journey of implementing, it later. But in brief, Raft is an algorithm that lets a cluster of machines work together to reliably do something. If you had a service that needed to stay up (and stay consistent), even if some of the machines in the cluster went down, then you might want to use Raft. | |
| | | | |
aphyr.com
|
|
| | | | | [AI summary] This technical blog post series introduces the concepts of distributed consensus and network partitions using the CAP theorem, while providing a tutorial on setting up a node cluster to experiment with database behavior during failures. | |
| | | | |
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. | |
| | | | |
seroter.com
|
|
| | | Today's links look at developer experience metrics you should track, why you need to rethink tech debt, and things you didn't dare ask about LLMs. | ||
