Microservices at Netflix Scale
Microservices at Netflix Scale
• Runtime Systems
• Container Runtime
https://media.netflix.com/en/company-blog/completing-the-netflix-cloud-migration
Data Center - Monolith
RDBMS
August 2008
First Principles
Buy vs. Build
● Use or contribute to OSS technologies first
Service A
● Available
● Partition Tolerance
● Tunable Consistency*
Multi-Regional Replication
Zone Zone
B B
500ms
Bi-directional
Region A Region B
Nightly compare & repair
Last, but not least - Billing
Microservices –
Benefits
Our Priorities
3. Efficiency
1. Innovation 2. Reliability
Innovation:
tight coupling doesn’t work
Develop
• Team A
• Team B Test Release
• Team C
• …
Innovation: Loose coupling
Develop,
Team A Test, Deploy,
Support
Develop,
Team B Test, Deploy,
Support
Develop,
Team C Test, Deploy,
Support
Support Architect
Run Design
End-end
ownership
Deploy Develop
Test Review
End-end ownership + velocity
Support Architect Support Architect
Support Architect Support Architect
A/B
Mid-tier Feature H
Test F
...
...
S S S S
Observe Orient
Act Decide
Edge Middle Tier & Platform
Zuul
EVCache
ELB
API
Cassandra
Playback
Reliability Matters
● We strive for 4 9’s of availability
…
99% availability 99% availability 99% availability
500
99% = 0.0657%
Microservice failure
FIT
Fault-Injection
Test Framework
Regional fail-over
x x
Regional fail-over
A word on containers
● Containers change the level of encapsulation
from VM to process
Docker
Docker S3
Registry
Docker
Registry
Registry
Ruslan Meshenberg
@rusmeshenberg