Going FaaSter: Function as a Service at Netflix
summary
Netflix runs a custom JS FaaS that packages a Node.js runtime into Docker images, manages them with Titus container scheduler, and stores versioned function images in a central registry. Developers use the "new" toolkit for local live-reload development and CI publishing; deploys can deploy to all three regions in under five minutes and use automated canary analysis. The platform auto-generates telemetry, dashboards and alerts so teams get automatic dashboards and alerts while central ops own the infra so teams are only on-call for business logic.
AI-written summary · about
chapters (10)
- 0:00Netflix introduction
- 1:28Data-driven development
- 3:38API and BFF architecture
- 6:12Evolution of infrastructure
- 9:15Titus container platform
- 12:49Runtime platform design
- 16:08Developer experience
- 22:09Production management
- 25:48Operations and monitoring
- 27:36Key lessons learned
related talks
26mGoing Faaster: Function as a Service at Netflix
33mFaaS 101
31mFaaS Meets Node.js Frameworks: Developing Cloud Native Node.js Applications at Speed
34mFaaS and Furious - 0 to Serverless in 60 Seconds, Anywhere
12mFaaSNet: Scalable and Fast Provisioning of Custom Serverless Container Runtimes...
31mFunction to Container - Building a FaaS Experience
39mFaaS: A Contemporary, Comparative Study
18mIntroduction of FaaS (Function as a Service) in starlingX