Alvaro Videla shows how to build a system that can ingest data produced at separate locations and replicate it across regions using RabbitMQ.
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.
Adam Rocska discusses how to approach an enterprise web front-end architecture, including quality assurance, code documentation, deployment, architectural planning and task delegation.
Jeff Johnson introduces Apollo, a hierarchical NoSQL data system meant to deal with Facebook's distributed storage needs.
Sponsored by Basho. Sean Cribbs discusses the theory behind several rich data types introduced with Riak 2.0 and then walking through some example applications that use them in popular languages.
Adrian Cockcroft discusses strategies, patterns and pathways to perform a gradual migration towards modern enterprise applications based on cloud, microservices and denormalized NoSQL databases.
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.
Terena Bell underlines the importance of designing applications for multiple languages including right-to-left ones in an age of rapid globalization.
Gilad Bracha keynotes on what's keeping web technologies from being on par with their native counterparts.
Shawn Gandhi provides an overview of the key scenarios and business use cases suitable for real-time processing, and how developers are using AWS Kinesis to shift from a traditional batch-oriented approach to a continual real-time data processing model.
Jeff Hodges discusses tactics and strategy for creating distributed systems today and a little about what the future holds.