Ruslan Meshenberg discusses Netflix's challenges, operational tools and best practices needed to provide high availability through multiple regions.
Dianne Marsh describes how Netflix' tooling, especially the continuous delivery system, allows them to build scaffolding enabling software developers to make the decision to push the button for prod deployment - and helps them to recover if necessary. As a result, they can run fast, trusting their tooling and culture.
Roy Rapoport discusses canary analysis deployment and observability patterns he believes that are generally useful, and talks about the difference between manual and automated canary analysis.
Carl Quinn explains how Riot Games built a cloud platform based on the Netflix OSS stack plus a number of other extensions including Dropwizard, Eureka, Archaius, Asgard, Edda, etc.
Jafar Husain, Matthew Podwysocki teach developers to think about events as collections, demonstrating some basic collection operations to express complex asynchronous programs as simple expressions.
Jafar Husain explains how Netflix uses reactive programming to build and consume REST endpoints, and how they work around the limitations of the HTTP protocol to create high-performance REST APIs.
Sudhir Tonse presents Netflix' composable PaaS built with several components that have been open sourced.
Xavier Amatriain discusses the machine learning algorithms and architecture behind Netflix' recommender systems, offline experiments and online A/B testing.
Dianne Marsh presents the open source tools used by Netflix to keep the continuous delivery wheels spinning.
Ben Christensen describes how the Netflix API evolved from a typical one-size-fits-all RESTful API designed to support public developers into a web service platform optimized to handle the diversity and variability of each device and user experience. The talk will also address the challenges involving operations, deployment, performance, fault-tolerance, and rate of innovation at massive scale.
Jeremy Edberg discusses how Netflix designs their systems and deployment processes to help the service survive both catastrophic events like zone and regional outages and less catastrophic events like network latency and random instance death.