ADR002: Use Multiple Repositories instead of one Large Repository

Context and Problem Statement

Should we use one large repository for all components of the project or structure this into multiple smaller repositories?

Chosen option: "Multiple Repositories", because it comes out best (see below)].

How to split the components into repositories will be decided throughout the runtime of the project.

Initially the following repositories were identified:

No single place to search for things, a little familiarity with the repository structure might be needed
Potentially more effort when setting up CI and testing infrastructure

Good, because it makes implementing dependencies between modules easier
Good, because it provides a single place to search for things
Bad, because it can become large and difficult to manage
Bad, because it keeps things that should be loosely coupled in the same place which might promote tighter coupling
Bad, because tagging a release of a component will unnecessarily include the rest of the repository
Bad, because changes to a component may accidentally impact other components
Bad, because the commit history is mixed for all components
Bad, because a single commit may change multiple components making tracking these changes harder
Bad, because the CI pipeline would need to identify the changed components to avoid triggering tests for all other components
Bad, because clone times might be much higher

Good, because it keeps the individual repositories simpler
Good, because it allows proper separation of modules
Good, because it allows proper tagging of releases
Bad, because implementing dependent changes in separate components becomes harder
Bad, because it makes finding individual pieces of code potentially harder if the repository is unknown