Protect downstream services from dublicated data in a microservice architecture
How can a microservice environment be protected from being polluted by duplicated data?
Should I join or split these microservices that use the same database?
I am developing an App for restaurants to manage the products they have and the orders from the costumers. So I’m facing issues when designing the microservices arch. I thought of having one ProductManagementService and another OrderService. But the problem I am facing is that the OrderService should have acces to the Products table from my databas and to access info like their prices and so does the ProductManagementService for obvious reasons.
Jobs in a microservice architecture
I’m currently developing two different REST services to be consumed at different points in time and serve different business purposes. Let’s name these service A and service B.