Looking back on migrating 30 microservices to a monorepository
summary
Migrates roughly 30 microservices into one monorepo while preserving Git history and keeping user-facing systems running; migration uses an automated six-line migration script to import repositories, adds CI gating with per-service checks and lightweight integration tests, and wires canary/preprod deployments so each service finalizes in about five minutes while some CI runs take ~13 minutes. Result is a single-repo layout, scripted branch/tag handling, and an automated deployment pipeline that cuts manual merge pain and avoids visible downtime.
AI-written summary · about
chapters (11)
- 0:00Microservices migration intro
- 3:00Separate repo challenges
- 6:13Code review bottlenecks
- 9:53Monorepo approach choice
- 13:27Monorepo migration tech
- 18:08Deployment improvements
- 24:58Automating monorepo deploy
- 27:47Testing migrated services
- 31:36Team collaboration benefits
- 37:07Monorepo access management
- 41:30Final thoughts & Q&A
related talks
25mMicroservices, Monorepos, and the Efficient Build Processes
40mOne Codebase to Rule Them All: A Monorepo Journey
19mEscaping Chaos: Strategies to Move from Polyrepo to Monorepo
01h 00mUsing Monorepos for Scalable Apps
48mMicroMonolith
23mOn the road from Monolith to Micro
51mBig microservices, small team a painful story
52mMicroservice Migration Roadmap