If you deal with distributed, fault-tolerant systems, you've sooner or later come across the "Reactive Manifesto" meet (if you haven't so far, you have now: "http://www.reactivemanifesto.org/"). But, as befits a manifesto, it sets out a programmatic vision, without providing detailed explanations and guidelines for implementation.
In this talk I discuss the reactive traits, and try to bring it down a level to technical properties: What is Reactive code, how do I put the principles into practice, and what are anti-patterns, which are to be avoided in reactive systems? And what does this all have to do with functional programming?
* JVM Implementation Challenges ("Threads are passé"): https://www.jfokus.se/jfokus15/preso/JVMChallenges.pdf
* The Problem With Threads: http://www.eecs.berkeley.edu/Pubs/TechRpts/2006/EECS-2006-1.pdf
* Life Beyond Distributed Transactions
PowerPoint: http://blogs.msdn.com/b/pathelland/archive/2007/11/25/presentation-of-life-beyond-distributed-transactions-an-apostate-s-opinion-at-teched-emea-at-barcelona.aspx (Link unten auf der Seite)
* Java Application Servers Are Dead:
Artikel: http://jaxenter.com/java-application-servers-dead-1-111928.html und http://jaxenter.com/java-application-servers-dead-112186.html