"Scaling A/B testing on Netflix com with Node.js"
summary
Netflix uses Node.js to resolve conditional front end dependencies at build time and request time, avoiding prebuilding a combinatorial blowup — about 2.5 million packages from hundreds of concurrent A/B tests — by authoring annotations with NF-include, scanning with a build-time asset registry, and assembling packages via a runtime packager. Registries bundle file contents, deploy to CDN, and serve concatenated JS/CSS from memory in less than five milliseconds, and the system is in production use.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:31Alex Liu
- 0:47Background
- 1:38Multivariate Av Testing
- 6:38Conditional Dependencies
- 8:51Asset Registry
- 10:37Packager
- 10:48Api
- 12:18Recap Using Visuals
- 13:45Hash Attribute and File Size
- 18:16Learnings
related talks
22mObservable Node.js Applications
31mKeynote Panel: Node.js at Massive Scale
27mBreaking the monolith with Node and Docker at Netflix
26mGoing Faaster: Function as a Service at Netflix
29mBreathe Into the Node.js
31mNode.js that's hugely reliable, fast, and scalable
31mGoing FaaSter: Function as a Service at Netflix
13mLessons learned in production
