![data duplicacy data duplicacy](https://i.ytimg.com/vi/gcAlms2K5A0/maxresdefault.jpg)
![data duplicacy data duplicacy](https://1.bp.blogspot.com/-V4-y0HF5L5U/V7STi3JpKTI/AAAAAAAAFYg/n6LaEz1RsK0sMrIVvlWIkmpu03pcp_NUgCLcB/s1600/Untitled408.png)
Microservice should communicate via events using publisher/subscriber model and topics. Another option could be when the data is required by the other 2 services make a call and get it from Order Service, but that is making it highly dependent and getting the data over network for each operation.Ĭan anyone suggest what would be ideal to do in such case. Another option could be given each of these service uses the same data is clubbing all of them into 1, but with that I again create a big service which if goes down will stop all 3 functionalities and is against SRP. As each of these functionalities have there respective UI for configuration and runtime engine to derive the output and most of the time changes only comes in these respective function blocks, I thought of creating the separate microservices.Ĭreating the separate microservice would need data(Parts and Features) to be duplicated. If the order contains part A and Feature A then perform X operation.
![data duplicacy data duplicacy](https://forum.duplicacy.com/uploads/default/original/1X/ce7e6c7a50cfa91961c311c1133ff225188ec8d3.png)
Now I have other 2 functionalities which uses the Parts and features to derive some runtime value say I have a service which receives Customer order say build a car with these parts and features. While scoping the microservice I am unable to decide whether I should go for a data duplication between services or ignore SRP by clubbing all requiring the same data into 1 service. I am new to microservices and trying to break up a big monolithic application into microservices.