# Advantages and Disadvantages of a Monolithic Repository * Date read - 2020-01-11 * Paper - [Advantages and Disadvantages of a Monolithic Repository](https://people.engr.ncsu.edu/ermurph3/papers/seip18.pdf) ## Notes * Advantages of monorepos * Forced consistency is viewed as a benefit of monorepos even though this is related to the *lack of flexibility* in monorepos compared to multi-repos * Ability to search for code is important to both code quality and velocity * Advantages of multi-repos * Flexibility of tooling * Stable versioning * Diamond dependencies ## Related papers * [Cohesive and Isolated Development with Branches](http://earlbarr.com/publications/gitbranches.pdf) * Ease of branching seems to be one of the major contributors in the adaption of DVCs, such as git and mercurial * Contrary to convention wisdom it is not the ease of development with distributed, as opposed centralised, development is *not* the key to the adaption of DVCs. * [Why Google Stores Billions of Lines of Code in a Single Repository](https://cacm.acm.org/magazines/2016/7/204032-why-google-stores-billions-of-lines-of-code-in-a-single-repository/fulltext) * Google Piper - in-house source control management system --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://wiki.dewaka.com/papers/cs/monorepos-seip18.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.