Too Long; Didn't Read
More and more developer teams are turning their backs on monorepos, instead choosing to liberate code to separate repositories. Many engineering teams have learnt the hard way that they don’t have the resources to support such architectural patterns. As the monorepo scales, deploying all software for every change quickly becomes impractical. Continuous Deployment is dependent on loosely-coupled services being separated by strictly-defined interfaces. Monorepos add complexity, risk and overhead to the process of deploying changes to software.