4 ms·
For the first concern you have things totally flipped. A monorepo actually seems best suited for a small company, with a small codebase and a small set of servi
by argonaut 9y ago
For the first concern you have things totally flipped. A monorepo actually seems best suited for a small company, with a small codebase and a small set of services.
If anything, the stage of company where it makes most sense to have many small repos is when you have a large company with multiple unrelated products, services, teams, etc.
- bonzini 9y agoYou're right that monorepos are just fine for small company. The problem is that at some point they don't scale without code review discipline and sophisticated tooling (such as Google's); thus there is a bottleneck where it becomes harder and harder to scale it until you get your tools right.
- argonaut 9y agoYes, but that point is probably when you have hundreds of engineers, at which point you can afford to have (and probably will already have) a few engineers working on internal tooling.