3 ms·
Got a feature that touches several modules? Instead of one massive build deployed once, you deploy each service. With dependencies you need to wait after each d
by Sankozi 3y ago
Got a feature that touches several modules? Instead of one massive build deployed once, you deploy each service. With dependencies you need to wait after each deployment to check if everything is ok. Instead of one big build and one deployment, you get quick build, deployment, check, quick build deployment, check...
So in case of microservices/microfrontends you gain minutes on build time but lose hours/days on deployment and verification.
- klysm 3y agoYes that is true, but the other side of that coin is that deploying changes to the interface between modules is now hard - that's the tradeoff space. If you have really clear interfaces with low churn then you probably have a net win, but in my experience it's really hard to get those interfaces right and that cost can end up beating your gains.
- Sankozi 3y agoNot sure what you mean. Changes to the interfaces in modular monolith are much easier than in microservices. You just release new version with updated interfaces - no need for versioning if you update interface and its usages. In case of microservices you must do versioning and either have to keep and support old version of the interface or spend some time to determine when to remove it.
- klysm 3y agoOops I replied to the wrong comment. I meant to reply to the parent and was trying to say the same thing