
A technical follow-up covering the internals of Raft, the actual RPCs, every server's state, what happens in each failure mode, and the edge cases around commitment, leases, and reconfiguration that the paper works hard to get right.
Go Beyond! Plus Ultra!
Software engineer working in Go. I write deep dives on Go internals and distributed systems, the goroutine scheduler, channel patterns, and what it takes to build reliable backend infrastructure. Currently going deep on distributed systems, AWS, and consensus.
Markdown supported · ⌘↵ to post
No responses yet.