News for hackers. Stuff that matters.
Re:Why Google Stores Billions of Lines of Code in a Single R... by spankalee on Sunday February 12, 2023 @06:51PM (#34768476)
Even so, the cost is often outrageously high.

No to mention that if you're the first team to import a third_party library, you own it and other teams can add arbitrary cost to you updating it. You have to be very aggressive with visibility and SLAs to work around this.

Re:Why Google Stores Billions of Lines of Code in a Single R... by admax88qqq on Sunday February 12, 2023 @07:44PM (#34768823)
You're basically just describing all the pain with pulling in a dependency regardless of monorepo or not.

If the third party dependency does not add enough value to justify the cost then don't add it.

Re:Why Google Stores Billions of Lines of Code in a Single R... by spion on Monday February 13, 2023 @01:33AM (#34770775)
In a multi-repo setup you can upgrade gradually though, tackling the services that need the upgrade the most first. Can you do that in a monorepo setup?
Re:Why Google Stores Billions of Lines of Code in a Single R... by onion2k on Monday February 13, 2023 @02:39AM (#34771085)
In a multi-repo setup you can upgrade gradually..

This also means services can be left to rot for years because they don't need to be upgraded, while all the infrastructure changes around them, which is a giant pain when you do eventually need to change something.

If you have a multi repo architecture you absolutely need both clear ownership of everything and well planned maintenance.

Re:Why Google Stores Billions of Lines of Code in a Single R... by ec109685 on Monday February 13, 2023 @02:43AM (#34771101)
The total pain is the same though.
Re:Why Google Stores Billions of Lines of Code in a Single R... by 8note on Monday February 13, 2023 @01:40AM (#34770804)
With multirepo setups, you don't necessarily need to update the package for all code at all.

Instead, some newer package completely replaces an old one, with no relation to the old dependency package, or with a dependency on some future one, and both can run at the same time while turning the old one off