Netflix embraced cloud computing to achieve scalability, unlimited performance, and high availability for its streaming services. It experimented with both relational and NoSQL databases before adopting NoSQL for most important functions. Netflix developed techniques like "Chaos Monkey" to test fault tolerance and moved to a microservices architecture in the cloud to enable graceful degradation during outages. Its goal was to achieve 99.99% availability with less than 30 seconds of downtime per week at peak traffic.
3. Netflix Service Unavailable Database Crashed
Rest assured that the right people
are losing sleep to fix this problem!
We expect to resume service in approximately 72h
12 Aug 2008 03:12am
17. Phase Components Data & Prerequisites
Trial (2009) Streaming Player Content keys (RO)
Membership status (RO)
Development Member product Content catalog (RW)
(2010-11) pages and APIs Personalization data
(RW) & recs algorithms
AB Test data (RW)
Followthrough Account and Membership data (RW)
(2011-12) membership
Final (2013) Payments PCI and SOX data
40. Redundancy
A B C
Zone Zone Zone Cassandra
A B C
S3 Backup
Redundancy
Across Availability Secure Cloud
Zones Backup
Storage Redundancy
Across
40
Regions, Vendors
45. Netflix at 2012 re:Invent
Date/Time Presenter Topic
Wed 8:30-10:00 Reed Hastings Keynote with Andy Jassy
Wed 1:00-1:45 Coburn Watson Optimizing Costs with AWS
Wed 2:05-2:55 Kevin McEntee Netflixs Transcoding Transformation
Wed 3:25-4:15 Neil Hunt / Yury I. Netflix: Embracing the Cloud
Wed 4:30-5:20 Adrian Cockcroft High Availability Architecture at Netflix
Thu 10:30-11:20 Jeremy Edberg Rainmakers Operating Clouds
Thu 11:35-12:25 Kurt Brown Data Science with Elastic Map Reduce (EMR)
Thu 11:35-12:25 Jason Chan Security Panel: Learn from CISOs working with AWS
Thu 3:00-3:50 Adrian Cockcroft Compute & Networking Masters Customer Panel
Thu 3:00-3:50 Ruslan M./Gregg U. Optimizing Your Cassandra Database on AWS
Thu 4:05-4:55 Ariel Tseitlin Intro to Chaos Monkey and the Simian Army
46. We are sincerely eager to
hear your feedback on this
presentation and on re:Invent.
Please fill out an evaluation
form when you have a
chance.
47. We are sincerely eager to
hear your feedback on this
presentation and on re:Invent.
Please fill out an evaluation
form when you have a
chance.
Editor's Notes
#26: Make clear its still tentative, not a committed project longer term