Panel discussion: Mono-repo Vs. Multi-repo Vs. Hybrid
summary
Panelists argue concrete tradeoffs: monorepo wins at coordination when a system has dozens of packages (they cite ~20 nodes and scaling pains beyond that), multi-repo gives clearer ownership for microservices, and start mono then split is a common migration path—one team used git submodules as an interim. Repeated claim: the bottleneck is VCS and orchestration tooling—Facebook/Google build custom systems because git indexing breaks at scale—so tooling is the real problem, not ideology.
AI-written summary · about
chapters (4)
related talks
40mMonorepo or Polyrepo: What's the Right Choice for You?
16mHow We Moved to a Monorepo
46mWe Solved All Modular Project Problems. Want the Same?
08mLightning Talk: Managing the ‘Git’ Half of ‘GitOps’: How to Structure...
01h 00mExtracting the monorepo
46mPanel Discussion: The number of orche
06mHow I Learned to Stop Worrying and Love the Mono Repo
25mMicroservices, Monorepos, and the Efficient Build Processes