Re:Josh: Get the advantages of a monorepo with multirepo setups
by dboreham on Thursday July 15, 2021 @11:40AM
(#27846012)
Monorepo is an alternative to having binary dependencies with a registry scheme such as npm or maven (at the organization level). It's essentially only workable with tooling support none of us has (unless you work for Google or one of the few other shops that have said in-house tooling). It isn't a workable approach using stock git or github (but that won't stop people trying nor claiming to the contrary).
[ Parent
| on HN ]
Re:Josh: Get the advantages of a monorepo with multirepo setups
by mumblemumble on Thursday July 15, 2021 @12:17PM
(#27846432)
I wouldn't want to do it at Google's scale without Google's tooling. But my experience has been that, at the scales I've worked at (no more than a couple million LOC across the organization), the limiting factor isn't source control, it's the build system. Maven, for example, doesn't really understand monorepos, so it can be a bit difficult to figure out a how to implement a policy for deciding what needs to be built when that's less heavy-handed than, "build everything always."