Building the World's Largest Studio at Netflix
summary
Studio engineering builds production tooling and microservices to turn spreadsheets into platformed apps: a 60-person team bootstraps apps with Newt, gives SPAs single sign‑on via Bolt and Meacham (JWTs), rips out Devise, and centralizes authz in Protego and Starship. Pipelines use Spinnaker and Jenkins, gRPC clients enable polyglot services, a JSON API serializer runs 25–40x faster than AMS, and Netflix spends about $8bn on originals while subscribers climb from 100m to 118m.
AI-written summary · about
chapters (19)
- 0:00Start
- 0:44Why I'M Here Today
- 6:47First Ever Netflix Original
- 7:37Origin Story
- 9:35Why Do We Choose Ruby To Build the Netflix Video
- 10:35Why We Chose Ruby
- 11:59Optimizing for the Number of Users
- 16:22The Netflix Workflow Toolkit
- 17:02Spinnaker
- 17:12Spinnaker Pipeline
- 18:10Orion
- 18:59Authentication
- 19:51Bolt
- 21:21How Does this all Work
- 23:03Protego
- 25:20Feature Flags
- 27:20Commenting
- 27:53Service Discovery
- 30:13Origin Story of Netflix
related talks
50mFast Delivery
18mBuilding Netflix's New Video Pipeline
28mHow Netflix Makes gRPC Easy to Serve, Consume, and Operate - Benjamin Fedorka, Netflix
53mHow Netflix Uses Java - 2026 Edition
34mThe Paved PaaS to Microservices
27mBreaking the monolith with Node and Docker at Netflix
08mMicroservices at Scale
59mJava microservices from Netflix OSS to Kubernetes