Jeff Johnson introduces Apollo, a hierarchical NoSQL data system meant to deal with Facebook's distributed storage needs.
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.
Michael Nygard discusses several loopholes in the CAP theorem that can be used to engineer practical, real-world systems with desirable features.
Paul Gross explains how Braintree deals with high availability for their Ruby application.
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.
Attila Narin discusses AWS concepts: Availability Zones, RDS Multi-AZ deployments, SQS and Auto Scaling, Elastic IP, load balancing, DNS, DynamoDB, Amazon S3, etc., and EC2 best practices.
Sean Cribbs compares ACID with BASE, explaining the virtues and tradeoffs of eventually consistent systems and what developers should know in order to feel comfortable working with EC systems.
Kresten Krab Thorup discusses cloud, multi-core, integration, high availability, and imperfect software starting from discoveries made while learning Erlang.
Martin Thompson discusses achieving high availability by using an event sourced architecture in which changes of the system’s state is captured as a sequence of events.
John Allspaw discusses fault tolerance, anomaly detection and anticipation patterns helpful to create highly available and resilient systems.
Mark McGranaghan presents how Heroku has designed, developed and operated cloud services providing high availability for their PaaS.
Gary Russell and David Turanski discuss creating HA architectures with Spring Integration using Cluster Controller and Strict Message Ordering, accompanied by demoes.