Re:Josh: Get the advantages of a monorepo with multirepo setups
by beagle3 on Thursday July 15, 2021 @11:30AM
(#27845880)
It’s basic git that breaks down, not the monorepo model.
And it’s less about LoC, and more about the number of files and how much binary stuff you put in your repo (and how often it changes). Git is really bad when binary data is involved.
Git has the facilities to keep monorepos clicking along (shallow clones and sparse checkout) but they aren’t along the “happy path”
Re:Josh: Get the advantages of a monorepo with multirepo setups
by romwell on Thursday July 15, 2021 @11:56AM
(#27846199)
That's why there's git-lfs[1] (large file storage)
Keeps the binaries out of your repo, replacing them with pointers
Re:Josh: Get the advantages of a monorepo with multirepo setups
by drjasonharrison on Thursday July 15, 2021 @11:45AM
(#27846060)
And many git repository hosting services, like bitbucket, have limits on how large your repository can be. Sometimes you can upgrade these limits. This often leads to fear of exceeding this limit and can lead to one repository per module.
Re:Josh: Get the advantages of a monorepo with multirepo setups
by vlovich123 on Thursday July 15, 2021 @11:55AM
(#27846190)
That’s an interesting claim considering Google, Facebook and Microsoft run monorepos. Heck Apple does too internally although just for the build team (snapshots of each project submitted to them, but it all goes into a mono repo)
Re:Josh: Get the advantages of a monorepo with multirepo setups
by romwell on Thursday July 15, 2021 @12:11PM
(#27846368)
I think the parent comment meant that multi-repo breaks down for large project, but made a typo.
With each project having its own repo, then you have to track the fact that Foobar 2.2 works with baizo 1.6-1.8 but not more recent versions.
Also conceptually it's easier when you are working with the client and the server at the same time, or the two mobile apps, and so on.
Of course people manage without this when the project has stuff that doesn't fit in a software repo (CAD designs, artwork, etc...there's a reason why that POS Perforce survives, for example). Solidworks has its own proprietary RCS that doesn't work with anything else.
IMHO if the project is relatively small (say <500K LoC) a monorepo is almost always the way to go. But with a big project it breaks down.