4 ms·
In this case, I'd say it's the opposite: monorepo as an approach works amazingly well for small teams all the ways up to huge orgs (with the right tooling to su
by CharlieDigital 2y ago
In this case, I'd say it's the opposite: monorepo as an approach works amazingly well for small teams all the ways up to huge orgs (with the right tooling to support it).
The difference is that past a certain level of complexity, the org will most certainly need specialized tooling to support massive codebases to make CI/CD (build, test, deploy, etc.) times sane.
On the other hand, multi-repos may work for massive orgs, but is always going to add friction for small orgs.
- dewey 2y agoIn this case I wasn't even referring to mono repo or not, but more about the idea of taking inspiration from very large companies for your own not-large-company problems.
- influx 2y agoI’ve used one of the Meta monorepos (yeah there’s not just one!) and it’s super painful at that scale.
- CRConrad 2y ago> ...one of the Meta monorepos (yeah there’s not just one! Eeh... Might be quite meta-, but really doesn't feel very mono-.