2 ms·
> Mono-repos are either a shortcut to avoid release management and dependency management In a small company, release and dependency management are pointless bu
by triceratops 6y ago
> Mono-repos are either a shortcut to avoid release management and dependency management
In a small company, release and dependency management are pointless busy work. And in larger companies, you have enough labor to manage monorepo tooling.
> Using multiple repos, one per shared product (library, SDK, web site, documentation package) is harder to manage because you need to manage your dependencies much better and pull in the correct versions for the current product.
This is the pointless busy work I was alluding to. See also: the diamond dependency problem. Meanwhile the benefits are unclear.
Multi-repos makes sense for entirely disconnected projects or products, or for collaboration in the open-source world. Most companies aren't going to run into significant issues with scaling a monorepo and they'll save a ton of work.