Katharina Probst talks about the situations in which server-side scripting is a good solution for applications. She describes Netflix’s first approach, which uses Groovy scripts.
Peter Bakas presents in detail how Netflix has used Kafka, Samza, Docker, and Linux to implement a multi-tenant pipeline processing 700B events/day in the Amazon AWS cloud.
Roy Rapoport discusses the power of alignment (or lack thereof) using real-world examples, his experience introducing Python in production, and the organizational structures and culture within Netflix
The authors present how lineage-driven fault injection evolved from a theoretical model into an automated failure testing system that leverages Netflix’s fault injection and tracing infrastructures.
Josh Evans discusses architectural patterns used by Netflix to enable seamless, multi-region traffic management, reliable, fast data propagation, and efficient service infrastructure.
Sangeeta Narayanan looks at the role of containers in simplifying and increasing the reliability of the process of releasing and operating the Netflix software.
Jafar Husain provides an inside look at the innovative Falcor, the open source JS data access framework that powers the Netflix UIs and the new UI design patterns it enables.
Josh Evans uses the Netflix Operations Engineering team as a case study to explore the challenges faced by centralized engineering teams and approaches to addressing those challenges.
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.