4 ms·
You're basically just describing all the pain with pulling in a dependency regardless of monorepo or not. If the third party dependency does not add enough val
by admax88qqq 4y ago
You're basically just describing all the pain with pulling in a dependency regardless of monorepo or not.
If the third party dependency does not add enough value to justify the cost then don't add it.
- 8note 4y agoWith multirepo setups, you don't necessarily need to update the package for all code at all. Instead, some newer package completely replaces an old one, with no relation to the old dependency package, or with a dependency on some future one, and both can run at the same time while turning the old one off
- spion 4y agoIn a multi-repo setup you can upgrade gradually though, tackling the services that need the upgrade the most first. Can you do that in a monorepo setup?
- onion2k 4y agoIn a multi-repo setup you can upgrade gradually.. This also means services can be left to rot for years because they don't need to be upgraded, while all the infrastructure changes around them, which is a giant pain when you do eventually need to change something. If you have a multi repo architecture you absolutely need both clear ownership of everything and well planned maintenance.
- ec109685 4y agoThe total pain is the same though.