Fred Hebert introduces two strategies for handling overload -load-shedding and back-pressure- along with different ways to make them work in Erlang focusing on the importance of planning for overload.
Benoît Chesneau discusses creating, scaling and reusing HTTP connections, summarizing techniques used to reduce memory usage in Erlang and ways to handle massive client connections efficiently.
Tim Fox discusses the design principles and motivation behind Vert.x and why the future is reactive.
Aviran Mordo introduces Wix's architecture, a highly available eventually consistent system, along with patterns for rendering many websites with a relatively small number of servers.
Brian Troutwine shares insight on using Erlang for a highly concurrent and very low latency bidding system implemented by Adroll.
Michael Dowden introduces JMeter and explains how to develop a data-driven methodology to determine some of the limits of a web application: max number of concurrent users, bottlenecks, etc.
Simon Marlow describes a concurrency-based system built with Haskell that allows front-end programmers to write business logic to access all the back-end services in a concise and consistent way.
Joe Armstrong describes the foundations of fault tolerant computation and the basic properties a system should have in order to be able to function in an adequate manner despite the occurrence of hardware and software errors, summarizing the key features of Erlang and showing how they can be used for programming fault-tolerant and scalable systems on multi-core clusters.
Nathan Marz discusses building NoSQL-based data systems that are scalable and easy to reason about.
Richard Crowley introduces Go standard library's HTTP packages, the relationship between JSON and Go's data structures, and Go's support for reflection, useful to create safe APIs.
Andrew Crump shows how to deploy and scale applications written in a variety of languages (including Clojure and Erlang) to Cloud Foundry.
Summly: An Award Winning Mobile App's Journey to the Cloud with Five-9s Availability on a Shoestring Budget
Eugene Ciurana describes the architectural choices, servers configuration, database, and caching systems that enabled Summly to achieve Five-9-Availability with deployments across transcontinental availability zones.