2 ms·
You need to do additional steps in both cases: With modules you need some sort of wrapper application to bring it all together. With microservices you need so
by treis 4y ago
You need to do additional steps in both cases:
With modules you need some sort of wrapper application to bring it all together.
With microservices you need some sort of network layer so that the microservices can talk to each other.
- regularfry 4y agoAnd also with modules you need the business processes to coordinate deployments across teams, because they all live in the same wrapper application. That's what stops them being independent. You don't restart the network every time you deploy a microservice.
- treis 4y ago>And also with modules you need the business processes to coordinate deployments across teams, because they all live in the same wrapper application. That's what stops them being independent. If we're being technical some languages support hot swapping modules so no restart would be needed. Setting that aside, restarting an application isn't anything that needs coordination today. You wouldn't even restart the application. You'd deploy a new version, swap over, and shut down the old version. >You don't restart the network every time you deploy a microservice. No, but something changes in the network configuration so that the other microservices are aware of the deployment.