We are basically in process of moving from monolith system to microservices and we avoided migrating monolith system all at once, or as they call it a big bang https://www.nginx.com/blog/refactoring-a-monolith-into-microservices/Since our microservices are built using DDD, where domain is persistence ignorant, we are considering a different approach for extracting a part of monolith to this new microservice.We would like to know what would the downside be of adding a new domain (microservice) on top of existing data layer?Adding a domain would help us achieve much wanted centralized business logic and since orms promote persistence ignorance, we could theoretically reuse the existing data layer (database), with possible modifications.
Migrating from monolith to microservices reusing data layer
domain driven design;orm;microservices;persistence