Going Faaster: Function as a Service at Netflix
summary
Netflix runs a homegrown JavaScript FaaS that packages a preassembled container runtime on top of Titus, versions function images in a central registry, and deploys them with canary deployments and auto-scaling so BFF teams get isolated, low‑latency services without owning infra. Local development uses a live‑reload desktop toolkit, deployments emit auto-generated metrics and alerts, and platform upgrades roll out uniformly — the platform claims production reliability and measurable developer velocity gains.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:32What is Netflix
- 1:17AB Testing
- 1:49Netflix Data Graph
- 2:10Audience Question
- 2:23Netflix API
- 3:04Frontend Pattern
- 4:11FaaS Evolution
- 7:19Runtime Platform Architecture
- 7:29Infrastructure as a Service
- 8:40Titus
- 11:04Function as a Service
- 12:33Package in Version
- 13:27Developer Experience
- 13:37Development API
- 14:54Platform Components
- 17:16Local Development
- 18:40Testing Isolation
- 19:49Deploying Functions
- 21:41Control Planes
- 23:51Lessons Learned
- 24:34Investing in Operations
related talks
31mGoing FaaSter: Function as a Service at Netflix
34mFaaS and Furious - 0 to Serverless in 60 Seconds, Anywhere
33mFaaS 101
31mFaaS Meets Node.js Frameworks: Developing Cloud Native Node.js Applications at Speed
15mFaastlane: Accelerating Function-as-a-Service Workflows
12mFaaS Platform Engineering with Wasm
12mFaaSNet: Scalable and Fast Provisioning of Custom Serverless Container Runtimes...
39mFaaS: A Contemporary, Comparative Study