Lessons learnt from working with the monorepo-style codebase Six months ago I landed a gig where the majority of the company’s code lived in a single repository, and I had a chance to experience it myself. Monorepo (or monolithic repository) is a way to store the source code of two or more independent, or loosely coupled, applications or services in a single code tree.
Having all the source code in a single location brings a bunch of potential benefits: Code sharing and collaboration
Although simplified refactoring and easy shared code management are great reasons to be lured into the concept of monorepo, it is not a silver bullet.