3 ms·
The API changes are mainly a problem (I think) if you have a monorepo, but not a mono-deploy; you can only get the full benefits of a monorepo if all your chang
by Cthulhu_ 5y ago
The API changes are mainly a problem (I think) if you have a monorepo, but not a mono-deploy; you can only get the full benefits of a monorepo if all your changes are deployed simultaneously and atomically.
Changing a model that is shared between different services (or a client / server) should be atomic. In practice, you need to think about backwards compatibility, and work in the three-step process outlined in the article (build and deprecate, switch over, remove deprecated code across a number of deployments / time).
If you don't have atomic deployments, that's one less argument in favor of monorepos.
- deleted 5y ago[deleted]
- jyounker 5y agoYou're using one specific definition of an API. Another definition of an API is the contract between a library and the calling code. The latter sort of API changes happen frequently (at least in places with monorepos), and they don't require phased deployments.