JavaScript
summary
Explains Uber’s concrete claim that JavaScript powers web frontends while core back ends migrate to Go/Java because Node’s 99th‑percentile latency and GC variance hurt ultra‑low latency services; lists tools actually used—express, react, Ring Pop, TChannel, Jaeger—and infrastructure built: an internal npm registry, scaffolding, a web platform serving 250+ sites; gives scale numbers (15,000 repos, 3,400 microservices, billions of trips) and shows the visualizations via deck GL working in production.
AI-written summary · about
chapters (14)
- 0:00Start
- 9:01Let Builders Build
- 9:53Uber Service Foundation
- 11:51Marketplace Gateway
- 12:16Logistics Challenges
- 12:52Uber Engineering Stack Evolution
- 14:00Monolith bad
- 22:56Lessons learned scaling Node.js
- 27:35Lessons learned scaling Uber
- 32:25Uber Web Platform built from Open Source
- 33:53Uber Web Platform added special sauce
- 36:17Frontend vs Backend
- 37:54React components for flexibility
- 40:25Visualization Frameworks
