From 02d3327a6a1b5ec755012b75ddc569d58882e7e5 Mon Sep 17 00:00:00 2001 From: Abhishek L Date: Tue, 9 Jun 2015 10:02:10 +0530 Subject: [PATCH] Adding Lamport's concurrency article --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index f886811..6fd5f7a 100644 --- a/README.md +++ b/README.md @@ -44,6 +44,7 @@ Must read papers on distributed systems. While nearly *all* of Lamport's work sh - [Notes on Distributed Systems for Young Bloods](http://www.somethingsimilar.com/2013/01/14/notes-on-distributed-systems-for-young-bloods/) - [High Scalability](http://highscalability.com/) Several architectures of huge internet services, for eg [twitter](http://highscalability.com/blog/2013/7/8/the-architecture-twitter-uses-to-deal-with-150m-active-users.html), [whatsapp](http://highscalability.com/blog/2014/2/26/the-whatsapp-architecture-facebook-bought-for-19-billion.html) - [There is No Now](http://queue.acm.org/detail.cfm?id=2745385), Problems with simultaneity in distributed systems +- [Turing Lecture: The Computer Science of Concurrency: The Early Years](http://cacm.acm.org/magazines/2015/6/187316-turing-lecture-the-computer-science-of-concurrency/fulltext), An article by Leslie Lamport on concurrency - [aphyr](https://aphyr.com/tags/Distributed-Systems), Posts on [jepsen](https://github.com/aphyr/jepsen) series are pretty awesome - [All Things Distributed](http://www.allthingsdistributed.com/) - Wernel Vogel's (Amazon CTO) blog on distributed systems - [Distributed Systems: Take Responsibility for Failover](http://ivolo.me/distributed-systems-take-responsibility-for-failover/)