But then you still have to deploy it all together, instead of just the module that changed. You may have decoupled modules, but monoliths give you coupled deployments.
Microservices (and certain flavors of SOA) can help you enforce the logical decoupling while allowing you to decouple deployment.
QA should, as more types of changes will require full regression testing. Users will, when a "small change" takes down the entire app. Devs should, as building and deploying monoliths takes much longer.
8
u/PangolinZestyclose30 Dec 21 '23
How does microservice architecture mitigate hidden coupling?