Building and Scaling Developer Environments at Stripe
summary
Stripe replaces long-lived, per-engineer EC2 dev boxes with per-branch short-lived EC2 instances that keep the authoritative source on the instance and detach state to cheap storage. VS Code Remote + Sorbet LSP runs on the remote box, a service runner spawns backend services, and a standby pool plus EBS snapshot/attach flow cuts startup latency. Problems: rsync and service startup cause slow branch switches, cold LSP cache misses on resume, and shared staging hijacks break isolation; about one third of engineers have migrated so far.
AI-written summary · about
chapters (7)
- 0:00Stripe’s dev environments intro
- 1:23Original hybrid setup
- 7:26Branch-specific dev boxes
- 15:32Advantages of branch model
- 22:05Scaling monolithic dev box
- 26:23Shared staging challenges
- 27:55Migrating to remote dev
related talks
26mScaling Enterprise Development with Cloud IDEs
32mImproving Dev Experience: How We Built a Cloud Native Dev Stack At Scale
34mImproving Developer Experience: How We Built a Cloud Native Dev Stack for 100s of Engineers
27mNavigating the Shift to Remote Developer Environments - A Year of Insights and Challenges
18mLeveraging Standardized Dev Environments for Peak Developer Velocity
28mEmbracing Remote Development for Local IDEs
54mSupercharge Backstage: Self-Service GitOps Staging Environments wi...
46mBuilding the IDE Golden Path