These days there is a clear trend to store your versioned files in a DVCS, a distributed version control system, which is typically Git. A DVCS is aimed at on one project, for example the sources of one library or one product. The Linux kernel, for which Git was originally designed, is almost the exception for its repository size and scope.

Keeping repositories separate has many advantages, especially for developers, however there are also challenges. Individual projects such as modules are not always independent but have interdependencies, which need to be managed. For DevOps teams this adds complications which are much easier addressed if all projects were stored in a single repository: a monorepo.

What is needed is a hybrid approach: individual repos to individual developers that are stored in the backend as a single monorepo for the DevOps teams. In this talk we are going to discuss the pros and cons of the different approaches and the requirements for a monorepo.