Why Google Stores Billions of Lines of Code in a Single Repository (2016)

Re:Why Google Stores Billions of Lines of Code in a Single R... by tzhenghao on Tuesday July 24, 2018 @11:52PM (#17606796)

Having worked at different companies adopting both monorepo and the multiple repos approach, I find monorepo a better normalizer at scale in consolidating all "software" that runs the company.

Just like what many commenters here have mentioned, the monorepo approach is a forcing function on keeping compatibility issues at bay.

What you don't want is to end up in a situation where teams reinvent their own wheels instead of building on top of existing code, and at scale, I think the multiple repo approach tends to breed such codebase smell. [1] I'm sure 8000 repos is living hell for most organizations.

[1] - https://www.youtube.com/watch?v=kb-m2fasdDY

[ Parent | on HN ]

Re:Why Google Stores Billions of Lines of Code in a Single R... by shiift on Wednesday July 25, 2018 @03:03AM (#17607369)

I really liked that talk! Lots of relevant information and I can definitely relate, working at a Amazon. Wouldn't say that we are hurt by all of the same problems (we have solutions that work very well for some of them), but we definitely are aware of them.

[ Parent | on HN ]