In recent years we have seen a significant increase in apps built using a microservices architecture. The main reason we select this approach is to have small teams that can work in isolation without having them trip over each other. Yet, this is an organizational problem, not a technical one. We can also build each service in different technology and scale independently.
Great post, one comment: structure your monolith on business modules, not technical ones (as controllers, services, daos...). This business modules couples with another ones and you can separate as independent: modules, packages, components, libraries, jars, microservices...
Great post, one comment: structure your monolith on business modules, not technical ones (as controllers, services, daos...). This business modules couples with another ones and you can separate as independent: modules, packages, components, libraries, jars, microservices...
Yes, DDD approach could be used here.