Nitesh Kant describes how embracing asynchrony in Netflix applications, from networking to business processing, creates gracefully degrading and highly resilient applications.
Hans Dockter discusses how to solve the challenges of standardization, dependency management, multi-language builds, and automatic build infrastructure provisioning.
Haley Tucker and Mohit Vora discuss the architecture at Netflix that makes streaming happen, while highlighting interesting lessons and design patterns that can be widely applied.
Spencer Gibb discusses the Spring Cloud abstractions and interfaces that an implementation might choose to implement: DiscoveryClient, LoadBalancerClient, Configuration and Bus.
Jon Schneider and Taylor Wicksell explain how they leveraged Spring Cloud Netflix inside of Netflix in applications and extended it further to incorporate fast properties, Atlas metrics, and more.
Justin Becker & Neeraj Joshi describe Mantis, discuss the challenges associated with designing for the cloud, processing billions of events, all while being cost sensitive.
Kolton Andrus presents how Netflix, in order to harden their systems, designed “Failure as a Service” to allow anyone to test and validate how their systems handle failure.
Matt Zimmer discusses architectural patterns -service decomposition, stateless application tiers, and polyglot persistence- and migration strategies used by Netflix.
Diptanu Choudhury discusses the design of Netflix’ distributed scheduler based on Mesos and Titan, focusing on bin packing algorithms, scaling in and out of clusters, fault tolerance, and redundancy.
Roy Rapoport shares some of the lessons Netflix learned building a monitoring system, the challenges, pitfalls and opportunities encountered along the way.
Sudhir Tonse discusses about the robust interprocess communications (IPC) framework that Netflix built (Ribbon).
Ben Christensen summarizes why the Rx programming model was chosen and demonstrates how it is applied to a variety of use cases.