3 ms·
The benefits of monorepos are (IME) all in people and organisation scale. For example, I've found it orders of magnitude easier to align tooling, quality, relea
by Joe8Bit 6y ago
The benefits of monorepos are (IME) all in people and organisation scale. For example, I've found it orders of magnitude easier to align tooling, quality, release and standards on a monorepo with 100's of 1000's of engineers working on it simultaneously.
The point you've made is a good one though, the idea of monorepos at small scale has come up a lot recently and I'm not sure the arguments for it are as compelling (I don't see many compelling arguments _against_ it either mind you). What I _have_ seen though is the pain large orgs go through going from multi-to-mono repos, I think Twitter did it recently and it was pretty painful.
- koonsolo 6y agoDo they use git or some other versioning system?
- Joe8Bit 6y agoMost orgs at that scale build their own tooling to make working with monorepos more ergonomic, in my experience. They're based on git (or other DVCS tools like Mercurial) but they allow you to easily do things like partial clones and company specific workflow tasks like submitting patches for review or tagging in weird and arcane ways. A small, illustrative example of this is the tooling that's built for Chrome's source code[0] with the depot_tools project [1]. [0]: https://chromium.googlesource.com/chromium/src/+/master/docs/mac_build_instructions.md#get-the-code https://chromium.googlesource.com/chromium/src/+/master/docs... [1]: https://chromium.googlesource.com/chromium/tools/depot_tools https://chromium.googlesource.com/chromium/tools/depot_tools