Member-only story
We explore the repository models ecosystem in our previous series of articles. We look at its definition, myths, and practices in other actors. It is still not enough to select a repo model.
We can jump too quickly to solutions that are hazardous without being clear on the problem to solve. A problem that is not solely technical and starts with the business.
This article aims to guide your repository model decision using a holistic quality engineering perspective and process.
Start with why, then for whom
It is worth investing time in the first place to clarify the “Why” of your initiative. Why are you considering the question of your code repo? Why would it be necessary for your company? What are you not doing while working on the repo question?
The first trivial case is for a start-up. The first lines of code need storage and, ideally, a proper structure from the start. When starting from scratch, a monorepo is usually the way to go. Some exceptions can exist starting with a larger team or number of IT components.
Evaluating the opportunity cost of a repo change for an existing company is more challenging. The added value is mainly in the mid-term, and while doing the changes, you can slow down the…
