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.
Sid Anand uses examples from LinkedIn, Netflix, and eBay to discuss some common causes of outages and scaling issues. He also discusses modern practices in availability and scaling in web sites today.
Ben Christensen explains how Netflix optimizes server’s interaction with more than 800 client devices by creating customized concurrent service endpoints with RxJava and Hystrix.
Ben Christensen describes how Neflix has optimized their API using a functional reactive programming (modeled after Rx) in a polyglot Java stack.
Daniel Jacobson shares advice on dealing with evolving APIs based on his experience with Netflix APIs.
Adrian Cockcroft presents Netflix globally distributed architecture, the benchmarks used, scalability issues, and the open source components their implementation is based upon.
Roy Rapoport discusses how Netflix uses metrics to monitor and manage their operating environment along with some notes about their event management system.
Jeremy Edberg presents the data stores used by Netflix and Reddit, some of the best practices and lessons for surviving outages.
Jeremy Edberg discusses running Netflix services on AWS: storage, streaming and scaling solutions, multi-region deployments, why cloud over private data center, and architectural snapshots.