You
Is a monorepo worth it for four services?
ChatGPT
At four services the deciding factor is how often changes cross a boundary:
| Monorepo | Multi-repo | |
|---|---|---|
| Cross-cutting change | one PR | coordinated PRs |
| CI complexity | needs filtering | simple per repo |
| Access control | coarse | per repo |
If most changes touch one service, separate repos stay simpler. If a typical feature touches three, the coordination cost outweighs everything else.
You
Does this still hold if I am working alone?
ChatGPT
It gets easier, not harder. A fair share of the difficulty is coordination, and that disappears. What remains is remembering your own decisions, which is what writing them down is for.