In this talk Jafar Husain and Matthew Podwysocki explore the Reactive Extensions (Rx) library which allows to treat events as collections. Also: how Netflix uses Rx on the client and the server.
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 Netflix API's evolution to a web service platform serving all devices and users, the challenges met in operations, deployment, performance, fault-tolerance, and innovation.
Jeremy Edberg discusses how Netflix designs their systems in order to survive outages, network latency and random instance failure.
Jeff Magnusson details some of Netflix' key services: Franklin, Sting and Lipstick.
Ariel Tseitlin discusses Netflix' failure-based suite of tools, collectively called the Simian Army, used to improve resiliency and maintain the cloud environment.