The document discusses Netflix's approach to continuous innovation through microservices and rapid software delivery. Key practices include a delivery pipeline, hands-free deployments, and real-time operational insights, emphasizing the benefits and complexities of distributed systems. The culture at Netflix supports this innovation with a focus on freedom and responsibility among teams.

1. Netflix Edge Services
Continuous Innovation
with Rapid Software
Delivery
Sangeeta Narayanan
@sangeetan
http://www.linkedin.com/in/
sangeetanarayanan
GitPro World April 2015
http://goo.gl/V2TVa1

2. Netflix Trivia Jeopardy

3. 34.9%
Share of peak downstream NA internet traffic
62 Million
Worldwide subscribers
10 Billion
Hours of content viewed in Q1 2015

4. Continuous Innovation
http://goo.gl/RXG4m8

10. http://netflix.github.io/

12. Continuous Innovation
http://goo.gl/VhokZV
Microservices
Continuous Delivery

13. Microservices
Single application comprised of a suite of
small, fine-grained services
❖ Loosely coupled
❖ Self-contained
❖ Independently managed and operated

14. Benefits of Microservices
❖ Increased velocity
❖ Optimized technology choices for each
service
❖ Improved resiliency through fault
isolation
❖ Greater developer efficiency

15. No free lunch!
❖ Complexity of Distributed Systems
❖ Greater Operational overhead
❖ Versioning/interfaces between services
❖ Testability

16. Benefits outweigh Costs
@ Netflix

17. Microservices @ Netflix

19. Availability
Zone
Availability
Zone
Availability
Zone
AWS
Region

20. Microservices
Single application comprised of a suite of
small, fine-grained services
❖ Loosely coupled
❖ Self-contained (Bounded Context)
❖ Independently managed and operated

21. Operate what you Build
❖ Delivery/Deployments
❖ Configurations
❖ Alerts
❖ On Call duties
❖ etc.
http://goo.gl/Q75Xdz

22. Operate what you Build
❖ Delivery/Deployments
❖ Configurations
❖ Alerts
❖ On Call duties
❖ etc.
http://goo.gl/Q75Xdz

23. Continuous Delivery
“The practice of building software so that it
is always in a state where it could be put
into production”
Attribution: http://martinfowler.com/delivery.html

24. ❖ Reduced risk because of smaller releases
❖ Easier to recover from errors
❖ Automation enables scaling
❖ Frees up capacity to work on core business
❖ Releasing software in a steady stream

25. Key Concepts
❖ Delivery Pipelines
❖ Feedback loops
❖ Hands-free deployments
❖ Insights & communication

26. Netflix API Delivery pipeline

27. Build
BakeTest
Canary Analysis
Deploy

28. Branching Strategy
Modeled after github-flow
Automated Pull Request Processing
Automated Patch Branching

29. Long lived branch; always
deployable
Feature branches; short-lived

30. Feedback Loops

31. ❖ Aggregate
Health Score
❖ >1500 metrics
❖ Configurable
❖ Multiple regions
Old$Code$(Baseline)$ New$Code$(Canary)$
~1%$Traffic$
Canary Analysis

33. http://bit.ly/1wQ8fPQ
Hands-free deployments

35. Red/Black Deployments

36. Old Code
Production Traffic

37. Old Code New Code
Production Traffic

38. Old Code New Code
Production Traffic

39. Automated Rollback

40. Pipeline Insights

43. Operational Insights
❖ Historical & Real time
views
❖ Rich, Dynamic data
visualizations
❖ Data aggregated from
various sources incl. real
time stream processing system
WebSockets
ServerSentEvents

44. RealtimeHistorical

48. http://goo.gl/1v8kev
Culture

49. Freedom and Responsibility
❖ Highly Aligned, Loosely
Coupled
❖ Management by Context, not
control

51. Continuous Innovation
Microservices
Continuous Delivery
Culture

52. Thank You