✳flâneur — a map of the web's best reading

Distributed systems theory for the distributed systems engineer | Paper Trail

the-paper-trail.org · 1,344 words · saved by 1 readers

Gwen Shapira, who at the time was an engineer at Cloudera and now is spreading the Kafka gospel, asked a question on Twitter that got me thinking. My response of old might have been “well, here’s the FLP paper, and here’s the Paxos paper, and here’s the Byzantine generals paper…”, and I’d have prescribed a laundry list of primary source material which would have taken at least six months to get through if you rushed. But I’ve come to thinking that recommending a ton of theoretical papers is often precisely the wrong way to go about learning distributed systems theory (unless you are in a PhD program). Papers are usually deep, usually complex, and require both serious study, and usually significant experience to glean their important contributions and to place them in context. What good is requiring that level of expertise of engineers? And yet, unfortunately, there’s a paucity of good ‘bridge’ material that summarises, distills and contextualises the important results and ideas in dist

Updated June 2018 with content on atomic broadcast, gossip, chain replication and more Gwen Shapira, who at the time was an engineer at Cloudera and now is spreading the Kafka gospel, asked a question on Twitter that got me thinking. I need to improve my proficiency in distributed systems theory. Where do I start? Any recommended books? - Gwen (Chen) Shapira (@gwenshap) August 7, 2014 My response of old might have been "well, here's the FLP paper, and here's the Paxos paper, and here's the Byzantine generals paper…", and I'd have prescribed a laundry list of primary source material whic

Explore this link on the map →

saved by

related reading