One repo is better because you can basically include the entire change set in 1 PR / gitref. Downside is it requires you come up with a structure and a bit of

One repo is better because you can basically include the entire change set in 1 PR / gitref. Downside is it requires you come up with a structure and a bit of discipline to maintain coherence. If you use codeowners and your CI can include other files, then most of the downsides go away, besides the repo size itself. Multirepo is a bit easier to understand per item. You can have one single CI file, and don't need codeowners, but you move a lot of burden to test, deploy and run. If your SCM supports codeowners and CI supports includes, I'd stick closer to mono-repos, and only break out things when it's helpful a D you obviously wouldn't change together. Think services rather than micro.