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.
Jeremy Edberg shares the need, the benefits, the pain points and the lessons learned moving Reddit and Netflix’s internal solution to Amazon AWS.
Daniel Jacobson covers the history of Netflix’s APIs, adaptation for the cloud, development and testing, resiliency, and the future of their APIs.
Siddharth Anand presents how Netflix’s architecture evolved from a traditional 3-tier configuration to a cloud-based one, detailing the scalability and fault tolerant issues encountered.
Carl Quinn presents the build and deployment architecture used by Neflix in order to provide content out of Amazon AWS.
Siddharth “Sid” Anand explains the technical details behind the move from Oracle used inside their data center to SimpleDB and S3 in the cloud, and from there to Cassandra.
Siddharth Anand overviews Netflix’s business model, then he explains why they chose Amazon AWS, and how they moved their data into the cloud using a NoSQL solution.