Monorepo Debate
Cluster focuses on discussions debating the pros and cons of monorepos versus multi-repo strategies, citing examples from companies like Google and Twitter, and their scalability for large codebases.
Activity Over Time
Top Contributors
Keywords
Sample Comments
What's wrong with a monorepo?
Why is a monorepo hugely beneficial here and what do you think they are doing right now ?
maybe not that easy if they use monorepos
Have you considered a monorepo? Normally only good for large, mature (infrastructure-wise) companies but it couldn't be worse, could it?
Just because it's a monorepo it doesn't mean it's centralized?
Google is a monorepo as far as I know, and they are doing fine.
It's enough i think once u tried to get monorepos done right for your project. It's a problem itself.
Having experienced both the monorepo approach (at Google and Lyft's L5 autonomous division) the and manyrepo approach (at Lyft's main rideshare division), my conclusion is that keeping as much code in a single repository as possible (i.e. a monorepo) is generally the best approach.The downside of manyrepos is that you often have to merge multiple changes into different repos in order to achieve a single logical change, and each of these changes requires a code review, waiting for CI
Monorepos create more issues than what they solve.
They have a monorepo - not monolithic app.