Gaining the Benefits of Monorepo in a Polyrepo World
summary
A concrete recipe for getting monorepo benefits while keeping many repos: use Gradle convention plugins to publish shared build logic, Gradle composite builds to substitute local projects for published artifacts, a centralized Gradle version catalog for one source of dependency truth, and Renovate to open update PRs. A real incident drove it: an eight‑library Coil upgrade produced 21 commits from five developers over 13 weeks and merged the day before freeze; the described setup reduces that coordination to local edits and automated catalog updates.
AI-written summary · about
chapters (14)
- 0:00Introduction and setup
- 3:00Polyrepo challenges explained
- 7:14Mono vs polyrepo differences
- 10:47Benefits of monorepo approach
- 11:10Gradle convention plugins
- 14:21Demo of convention plugins
- 16:50Convention plugin benefits
- 21:03Composite builds introduction
- 23:31Dependency substitution demo
- 27:59Version catalogs explained
- 29:01Automating dependency updates
- 31:28Renovate configuration
- 32:10Self-hosted Renovate setup
- 33:16Q&A and closing
related talks
35mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
31mMonorepos, Mainframes, and Modus Operandi Accepted
02h 29mPractical advice for building glorious monoliths
52mMonoliths to Modular: Navigating the Transition
52mMy Monolith Is Really Cool
39m7 Strategies for Building Majestic Monoliths
21mModernizing Monolithic Application: Isolation Before Independence
50mSplitting the Monolith at Leroy Merlin