/explore
|
You are here 
|
martin.kleppmann.com | ||
| | | | |
preethikasireddy.com
Distributed systems can be difficult to understand, mainly because the knowledge surrounding them is distributed. But don't worry, I'm well aware of the irony. While teaching myself distributed computing, I fell flat on my face many times. Now, after many trials and tribulations... |
|
| | | | | ||
| | | | |
decomposition.al
Back in May, I gave the opening keynote (my first keynote talk!) at the FLOPS 2022 conference. I talked about the work weve been doing in my group on using Liquid Haskell for verifying the correctness of distributed systems. |
|
| | | | | ||
| | | | |
davquar.it
In this introductory post on distributed systems we'll see some basic concepts such as: local and global states, consistent and inconsistent cuts, vector clocks, Chandy-Lamport's snapshot protocol. |
|
| | | | | ||
| | | | |
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. |
|
| | | |||
