How DevPod Became Uber's Primary Development Environment
summary
DevPod becomes Uber’s primary development environment by replacing slow local setups with Docker containers on Kubernetes, pre-cloned monorepo images and SSD-mounted host build caches that cut build times, remote build caches and artifact repos, and Kubernetes volume snapshot API to archive persistent disks to cold storage; five low-latency clusters and connection options (VS Code, JetBrains Gateway, terminal) support workflows, automated nightly updates plus feature flags and release channels handle rollouts, almost over two thirds of engineers actively using it and automated nightly updates eliminate manual version drift while total costs drop despite rising adoption.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:53Development at Uber
- 1:22Challenges at scale
- 2:35Devpod: Uber's CDE
- 3:52Performance out of the box
- 5:27Low latency
- 6:23Ready to go!
- 8:09Personalization
- 9:36IDE support
- 12:27Managing environments
- 14:01Managing costs
- 15:32Tables have turned
- 16:12Testimonials
- 16:32What's next?
- 17:09Summary
- 17:30Ending note
related talks
32mDeveloping on Containers with Dev Containers
40mBeyond Productivity: Scaling Cloud Dev Environments for Faster Feedback & Sustaina...- 32mDeveloping on Containers with Dev Containers
41mThe Future of Writing Software Happens in CDEs
46mCodespaces, Gitpod, Devpod: What cloud & container-based IDEs can do for you
15mOnboarding like Uber or Stripe is simpler than you think
24mRemote development can improve your developers remote work experience
29mGitpod: The End of Unnecessary Friction for Contributing to an OSS Project?