Notes on Distributed Systems for Young Bloods
I’ve been thinking about the lessons distributed systems engineers learn on the job. A great deal of our instruction is through scars made by mistakes made in production traffic. These scars are useful reminders, sure, but it’d be better to have more engineers with the full count of their fingers.New systems engineers will find the Fallacies of Distributed Computing and the CAP theorem as part of their self-education. But these are abstract pieces without the direct, actionable advice the inexperienced engineer needs to start moving[1]. It’s surprising how little context new engineers are given when they start out.Below is a list of some lessons
What the influencers are saying
-
Steve Klabnik
Distributed systems are hard: http://t.co/qf2zBbtu
-
Padmasree
RT @mabb0tt: great post by @jmhodges on distributed systems! - http://t.co/zRLVZYi0
-
wadearnold
Awesome! Thanks @jmhodges for taking the time to write Notes on Distributed Systems for Young Bloods http://t.co/emFUBQfS
-
Werner Vogels
Notes on Distributed Systems for Young Bloods /by @jmhodges - http://t.co/3rgEyYJT
-
Hilary Mason
distributed systems wisdom, from @jmhodges http://t.co/WUV1ng3g
-
Soren Macbeth
shut up and read this http://t.co/2zmURJch
-
David Harvey
RT @newsycombinator: Notes on Distributed Systems for Young Bloods http://t.co/51Fpb3mK
Related Reading
 |
To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. |
