In Microservices is it acceptable to have an API returning an Aggregate Root that was replicated?
Clash Royale CLAN TAG #URR8PPP In Microservices is it acceptable to have an API returning an Aggregate Root that was replicated? Imagine we have a microservice M1 with an aggregate root called Player and a microservice M2 with an aggregate root called Classification , now in the M1 we need to do some logic based on some property from Classification , now some steps to do that are: Player Classification Classification Ok, now imagine we have a view to add Players, and in that view is possible to choose the Classification of the new Player from a dropdown list. Now the question: Classification Player Should the dropdown list be populated with the Classifications that were replicated into M1 or from M2? As you can see, by using the data from M1 we would have to expose the Classification from M1 via an API, thus the title of the question. Classification 1 Answer 1 I believe both can be done and one ...