Download as PDF, PPTX
![Script isolation & node
❏ Groovy scripts run as
part of API process
❏ UI teams would like to
use other languages
(in particular node.js) API remote
service layer
Service client
libraries
UI/device
scripts (node)
Falcor
var response = model.get("todos[0..2]
['name','done']");](https://image.slidesharecdn.com/ticketmastertalkoctober2015-topublish41-151109151244-lva1-app6891/75/Evolving-the-Netflix-API-57-2048.jpg)
Uploaded byKatharina Probst
Evolving the Netflix API
The document outlines Netflix's evolution of its API, highlighting its goals of flexibility, resiliency, and scalability while supporting over 70 million subscribers across various devices. It discusses the implementation of a personalization engine and improvements in server-side scripting to enhance development and reduce network chattiness. Additionally, it identifies ongoing challenges such as breaking up monolith architectures and adapting to new interaction models within the API ecosystem.
More Related Content
Similar to Evolving the Netflix API
Evolving the Netflix API
- 1. Evolving the Netflix API KatharinaProbst Engineering Manager, API October 2015
- 2.
- 3.
- 4. Is it significant? ❏Peak downstream traffic in the US is almost 35%. ❏ Almost 70 Million subscribers worldwide and growing Source: http://www.sandvine.com/news/global_broadband_trends.asp
- 5.
- 6. Source: https://help.netflix.com/en/node/14164 Recent additions: Spain,Portugal, Italy Current availability
- 7.
- 8. Do we needa Netflix API?
- 9.
- 10. Uses ❏ Discovery ❏ Signup ❏Playback ❏ Internal teams only API
- 11. Goals ❏ Flexibility ❏ Resiliency ❏Scalability ❏ Excellent tools API
- 12. Goals ❏ Flexibility ❏ Resiliency ❏Scalability ❏ Excellent tools API
- 13. Lots of devices,lots of variety
- 14.
- 15. And just tomake things a little more interesting…. ❏ A/B tests ❏ profiles ❏ localization
- 16. What we felt wehad What we needed
- 17. ❏ Reduce networkchattiness ❏ Support device optimizations ❏ Enable faster development for internal users
- 18.
- 20. Discrete HTTP requestspay network tax repeatedly
- 21. Single, optimized request;pay network tax once
- 22. Single, optimized request;pay network tax once Client data assembly logic pushed to server
- 23. Add server-side scriptingcapability ❏ Enable independent development & device optimization ❏ Profit
- 24. ❏ UI (script)changes can happen independently ❏ Script changes can be pushed to running servers, so decoupled from API push schedule ❏ Server+UI changes usually involve API team Impact on velocity and collaboration
- 25.
- 26.
- 27. Goals ❏ Flexibility ❏ Resiliency ❏Scalability ❏ Excellent tools API
- 28. https://github.com/Netflix/Hystrix resilience patterns fordistributed sys
- 29. Hystrix Primer ❏ Protectionfrom and control over latency and failure from dependencies ❏ Stop cascading failures in a complex distributed system ❏ Fail fast and rapidly recover ❏ Fall back and gracefully degrade
- 30.
- 31.
- 32. API Personalization Engine Similar movies Movie Metadata Ratings User Info Instant Queue A/BTest Engine Beware Cascading Failure!
- 33.
- 34. Personalization Engine Similar Movies Movie Metadata Ratings User Info Instant Queue A/BTest Engine Fallback Response Local Fallback Avoids Cascading Failure! API
- 35. Personalization Engine Similar Movies Movie Metadata Ratings User Info Instant Queue A/BTest Engine Fallback Response Use FIT to test such failures API
- 36. Goals ❏ Flexibility ❏ Resiliency ❏Scalability ❏ Excellent tools API
- 37. Autoscaling & CapacityManagement http://nflx.it/1LvqLUi
- 38. AWS Controls Reactive,does not scale up fast enough
- 39. Fine-grained Control withScryer Complements AWS Controls ❏ Faster scale-up, improved cost ❏ Use reactive policy for organic scale down
- 40. Goals ❏ Flexibility ❏ Resiliency ❏Scalability ❏ Excellent tools API
- 41. Run 1% ofyour traffic on the new code and see how it does
- 42. ❏ Errors: 2xx,4xx, 5xx ❏ latency ❏ network ❏ busy threads ❏ load ❏ ... So you’ve run a canary. Now what? Control Canary
- 44.
- 45.
- 46. Quickly see statusof all clusters http://techblog.netflix.com/2015/09/moving-from-asgard-to-spinnaker.html
- 47.
- 49.
- 50.
- 51.
- 52. Real-time analysis http://www.slideshare.net/g9yuayon/qcon-talk-on-netflix-mantis-a-stream-processing-system Submit aquery, see requests in real time.
- 53. Looking ahead -current challenges ❏ Breaking up the monolith ❏ Script isolation ❏ Thin client libraries ❏ New interaction models
- 54.
- 55. Looking ahead ❏ Breakingup the monolith ❏ Script isolation ❏ Thin client libraries ❏ New interaction models
- 56. ● > 900active endpoints ● ~ 30 client libraries ● 78 thread pools ● high memory usage Breaking up the monolith
- 57. Script isolation &node ❏ Groovy scripts run as part of API process ❏ UI teams would like to use other languages (in particular node.js) API remote service layer Service client libraries UI/device scripts (node) Falcor var response = model.get("todos[0..2] ['name','done']");
- 58. Thin client libraries ❏Many client libraries contain a lot of business logic and have a lot of dependencies ❏ Move business logic and dependencies to server API remote service layer Service client libraries UI/device scripts (node) Falcor
- 59. Looking ahead ❏ Breakingup the monolith ❏ Script isolation ❏ Thin client libraries ❏ New interaction models
- 60. New interaction models ❏request/response ❏ request/stream ❏ fire-and-forget ❏ event subscription ❏ channel API remote service layer Service client libraries UI/device scripts (node) Falcor http://reactivesocket.io
- 61.