4 ms·
monorepo is very difficult to get right - and once you do, you are pretty much stuck with the language/tool choices since the switch usually takes months/years.
by sheeshkebab 9y ago
monorepo is very difficult to get right - and once you do, you are pretty much stuck with the language/tool choices since the switch usually takes months/years.
multirepo is a nightmare for changes spanning multiple repos, but the freedom of using the best tool for the job is much easier to achieve.
or so is my thinking about these from experience.
- icebraining 9y agoI think that's having a single codebase. You can have different projects using different languages on a single repo.
- TickleSteve 9y agoDon't confuse multi-repo with multi-language. Its very common to have multiple languages in a monorepo codebase.
- bengale 9y agoIn my experience the problem you're identifying there is an general failing to understand boundaries when designing the system. A language or framework shouldn't pervade every package, to aid this in my most recent large project we formulated a naming structure for packages that gave an indication of where they fit in, from a high level perspective, and the sorts of dependencies they should have.