These are the type of posts I come to hacker news for (sorry meteor evangelists and NSA watchdogs).<p>I'd also like to recommend the Spark Streaming Paper[0] for people interested in real-time distributed architectures.<p>0: <a href="http://www.cs.berkeley.edu/~matei/papers/2012/hotcloud_spark_streaming.pdf" rel="nofollow">http://www.cs.berkeley.edu/~matei/papers/2012/hotcloud_spark...</a>
A pretty good text to have around is <i>Distributed Systems Concepts and Design</i>[1]<p>[1] <a href="http://www.amazon.com/Distributed-Systems-Concepts-Design-Edition/dp/0132143011/ref=sr_1_1?ie=UTF8&qid=1383251499&sr=8-1&keywords=distributed+systems+concepts+and+design" rel="nofollow">http://www.amazon.com/Distributed-Systems-Concepts-Design-Ed...</a>
great list, and thank you!<p>how would you recommend printing these out and binding them for my own personal copy in dead tree form? i ask because i like having these sorts of things on the shelf for reading and referencing, and taking notes in. i also want to do this with the "Great Works in Programming Languages" [1]. i've been wondering if something like Kinkos' "Book Binding" [2] would be usful here, but then i worry about the fact that they may not print it for me because the papers are copyright someone else.<p>thoughts? suggestions?<p>1. <a href="http://www.cis.upenn.edu/~bcpierce/courses/670Fall04/GreatWorksInPL.shtml" rel="nofollow">http://www.cis.upenn.edu/~bcpierce/courses/670Fall04/GreatWo...</a><p>2. <a href="http://www.fedex.com/us/office/binding-finishing-laminating.html" rel="nofollow">http://www.fedex.com/us/office/binding-finishing-laminating....</a>
You might also like the "Think Distributed" podcast:<p><a href="http://thinkdistributed.io" rel="nofollow">http://thinkdistributed.io</a>
The languages section seems a bit trendy and misses a lot of old-school work that predates the popularity of the m/r paradigm. I would suggest additions like Linda and tuple spaces and Hoare's csp paper (also somewhat trendy at the moment but still old-school.)
It's interesting how many problems the blockchain data structure solves for distributed systems.<p>Bitcoin uses (and invented) the blockchain as a way to solve the double-spend problem of distributed e-cash systems. But the fact that the blockchain solves the consensus problem without any trust makes it a compelling data structure for many other use-cases as well.<p>Even if bitcoin fails as a currency, academics will be referencing Satoshi Nakamoto's paper [1] for a long time to come.<p>[1] <a href="http://bitcoin.org/bitcoin.pdf" rel="nofollow">http://bitcoin.org/bitcoin.pdf</a>
Michael Bernstein had a great talk on Distributed Systems Archaeology at RICON West yesterday. Video coming soon, but here are the notes:<p><a href="https://speakerdeck.com/mrb/distributed-systems-archaeology" rel="nofollow">https://speakerdeck.com/mrb/distributed-systems-archaeology</a>
This is great but does anyone have recommendations on getting started in distributed systems? I'm a lowly web developer and would like to get into this more.