Deployment Nirvana
summary
Describes running ~40 small services in Node, replacing circus with a homegrown service registry + HTTP proxy to stop collateral flapping and achieve zero-downtime deploys. Uses a port registry (seaport/portland), per-backend metrics, and routes requests to specific git SHAs so branches/commits act as versions. Solves coordinated releases by packaging a per-deploy “release version” map, notes inter-service versioning is still hard, and ships an open‑source tool currently running on personal servers.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:38The Web is changing.
- 4:45In the beginning, we wanted to build a software
- 5:09Moz Local
- 8:30The descent into madness.
- 9:16Circus
- 9:36Collateral Flap
- 10:35Deployment
- 10:58DMV + Seaport + Viaduct • Pile of home-rolled, loosely coupled services.
- 12:03is the greatest thing.
- 12:27is the worst thing ever.
- 13:25Service versioning "Solved" problem
- 14:15Service versioning redux
- 14:47Routing Layer Versioning
- 22:02Inter-service versioning . We build a Release version to encapsulate all Our services at a given revision
- 24:59Client Tooling
- 26:20Lessons learned
- 27:53Let's deploy better.
related talks
36mWild Microservices and Imaginary DevOps
26mPivoting your Pipeline from Monolithic to Microservices
19mScaling Microservices Development
36mCultivating a Microservice Culture Via Tooling
35mCloud Native Development Without the Toil
30mBringing Continuous Delivery to Open Source
47mDeploying Like a Boss: From 2 Servers to 20,000
01h 04mDeploying and Scaling Microservices