Answer is no. It is about where the shoe fits. If you become too heavily dependent on modules you risk module incompatibility due to version changes. If you a

Answer is no. It is about where the shoe fits. If you become too heavily dependent on modules you risk module incompatibility due to version changes. If you are not the maintainer of your dependent module you hold a lot of risk. You don't get that with microservices. If you focus too much on microservices you introduce virtualized bloat that adds too much complexity and complexities are bad. Modules are like someone saying it is great to be monolithic. Noone should upright justify an overly complicated application or a monolithic one. The solution is to build common modules that are maintainable. You follow that up with multi-container pods have them talk low level between each other. Stricking that exact balance is what is needed not striking odd justifications for failed models. It is about, "What does my application do?" and answering with which design benefits it the most.