Should you "go mono"?
It's a question that lots of companies in the dev community are discussing.
Developing large-scale codebases with multiple teams, can be a big headache. When a product reaches a certain size, developers often attempt to split it into multiple parts to address separation of concerns. But this 'multi-repo' approach has an impact on the overall developer experience, which is why teams are increasingly interested in a monorepo approach.
Our team wrote wrote a great article exploring the key concepts behind monorepos, including what they are, where they fit, and where they don’t. Check it out here.
Top comments (0)