For a service like Netflix, data is crucial. In this session, the Director of Cloud Platform Engineering at Netflix details how they chose and leveraged Cassandra, a highly-available and scalable open source key/value store. In this presentation they discuss why they chose Cassandra, the tools and processes they developed to quickly and safely move data into AWS without sacrificing availability or performance, and best practices that help Cassandra work well in AWS.

2. Netflix
AWS Cassandra

4. Netflix API – Growth in requests
25
Requests in Billions (per day)
20
15
10
5
0
Data Center Capacity

9. us-west-2
1c 1c 1a
1e 1d S3 1b
1d 1e 1b 1c
Durability (Quorum)
1c One instance:  1c 1a 1a
Availability zone: 
Replica set: 
1e 1d 1c 1b
1d 1e 1b 1c
1c S3 1a S3
us-east-1 eu-west-1

23. 23

24. 24

25. 25

26. 26

27. Client Writes/s by node count – Replication Factor = 3
1200000
1099837
1000000
800000
600000
537172
400000 366828
200000 174373
0
0 50 100 150 200 250 300 350

30. 50 Number of production clusters
15 Number of multi-region clusters
4 Max regions, one cluster
101 Total TB of data across all clusters
780 Number of Cassandra nodes
72/32 Largest Cassandra cluster (nodes/data in TB)
250k/800k Max read/writes per second on a single cluster

35. http://techblog.netflix.com
http://netflix.github.com

36. 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.