Escaping Chaos: Strategies to Move from Polyrepo to Monorepo
summary
A UK banking app developed by 60+ Flutter developers grows to 60+ packages across separate Git repos, causing broken main branches, long CI waits, and painful cross-repo edits. The proposed plan scripts a big‑bang import with preserved history using git subtree, configures CI/CD and Melos, tests performance on a monorepo clone, then runs a short code freeze to switch everything at once. The migration is planned but not executed yet, so results are pending.
AI-written summary · about
chapters (10)
- 0:00Polyrepos vs monorepos
- 1:52Polyrepo problems in large projects
- 5:08Polyrepo workflow issues
- 8:47Dependency management challenges
- 10:34Polyrepo use cases
- 11:57Migration strategies to monorepo
- 13:44Gradual migration drawbacks
- 14:30Big bang migration risks
- 16:38Preparing for monorepo migration
- 18:03Migration status and plans
related talks
07mStreamlining Development with the Monorepo Ecosystem
40mOne Codebase to Rule Them All: A Monorepo Journey
16mManaging multiple packages in a monorepo
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
44mLooking back on migrating 30 microservices to a monorepository
19mKeynote: Why Monorepos
01h 00mUsing Monorepos for Scalable Apps
37mTaming Legacy: Refactoring Patterns for Large Flutter Codebases