2. About Netflix
● 109M+ members
● 2000+ employees (1400 tech)
● 80+ countries
● > 100M hours watch per day
● > ⅓ NA internet download traffic
● 500+ Microservices
● 100,000+ VM’s
● 3 regions across the world
4. Why does Netflix open source?
Improve Engineering
● Great feedback from wider community
● Collaborate through open code
Recruit new and retain engineering talent
● Hard problems are openly worked on
Industry Alignment
● Content and cloud technologies
10. A truly global service
● Replicate data across
regions
● Be able to redirect traffic
from region to region
● Be able to migrate
regional traffic to other
regions
● Have automated control
across regions Flux Demo
11. Testing is only way to prove HA
● Chaos Monkey
○ Kill instances in production - runs regularly
● Chaos Kong
○ Kill entire region and shift traffic globally
○ Run frequently but with prior scheduling
18. Dynamic, Web Scale & Simpler Security
Security Monkey
● Monitors security policies, tracks changes, alerts on situations
Scumblr
● Searches internet for security “nuggets” (credentials, hacking discussions)
Sketchy
● A safe way to collect text and screenshots from websites
Sleepy Puppy
● Delayed cross site scripting propagation testing framework
Lemur
● x.509 certificate orchestration framework
Stethoscope
● Automated security monitoring and alert for employees
19. What did we not cover?
Big Data, Data Persistence and UI Engineering
● Big Data tools used well beyond Netflix
● Ephemeral, semi and fully persistent data systems
● Recent addition of UI OSS and Falcor
Other parts of the Netflix business
● Personalization and Algorithms
● Content Encoding and Delivery
● Studio and Partners facing applications