5 ms·
You can do that with a many-repo, provided you have the right tooling. In fact, I'd argue Google's advantage is in the tooling they built around the repo, not t
by Aissen 9y ago
You can do that with a many-repo, provided you have the right tooling. In fact, I'd argue Google's advantage is in the tooling they built around the repo, not the monorepo itself. E.g how fast you can find all your dependents in the whole repo.
- boulos 9y agoNot really, as there isn't the ability to atomically commit your changes. With 70000+ full-time employees code is getting checked in all the time. Atomicity is extremely valuable.
- yoz-y 9y agoYou can. You have many repos and one top level repository with submodules. Edit: And although this is a multi step process, it still allows you to de-couple modules and work on them separately.
- kadenshep 9y agoIt's like the people commenting about this forget what distributed means. You can have multiple repos, but you can still have a gate way/"source of truth" repo. You can run tests and whatever else on it just like you do in a "monorepo." The power behind Google's/Facebook's choice isn't and will never be the mono repo. It's specifically the tooling they built around their choice.
- sah2ed 9y agoThe 70,000+ number you cited includes engineers and non-engineers but surely, the actual number of engineers that need commit access will be much lower.