Question: what is the benefit of implementing a microservice (uS) infrastructure plus having a huge MDM system on top/in parallel? If the different uS do hold all relevant data and do own that data by the sense of being really responsible and the "master"-system for that data, then there is no point in having that data within a MDM software on top.

Example: service A is the only responsible system for data A and is caring about distributing that data A to any system in need of A. Service A could be a uS with a RESTful HA abstraction of its data. Now: let´s say a user recognizes an error in data A within system B. In order to maintain the data consistency and source of truth, that user is not allowed to change data A in system B, but he needs to change it in service A because service A is the master for data A. In such an architecture: why would you need a dedicated MDM. What do you think?

Question: what is the benefit of implementing a microservice (uS) infrastructure plus having a huge MDM system on top/in parallel?

If the different uS do hold all relevant data and do own that data in the sense of being really responsible and the "master"-system for that data, then there is no point in having that data within a MDM software on top.

Example: service A is the only responsible system for data A and cares about distributing that data A to any system in need of A. Service A could be a uS with a RESTful HA abstraction of its data. Now: let´s say a user recognizes an error in data A within system B. In order to maintain the data consistency and source of truth, that user is not allowed to change data A in system B, but he needs to change it in service A because service A is the master for data A.

In such an architecture: why would you need a dedicated MDM? What do you think?

Question: what is the benefit of implementing a microservice (MS) infrastructure plus having a hugh MDM system on top/in parallel? If the different MS do hold all relevant data and do own that data by the sense of being really responsible and the "master"-system for that data, then there is no point in having that data within a MDM software on top.

Example: service A is the only responsible system for data A and is caring about distributing that data A to any system in need of A. Service A could be a MS with a RESTful HA abstraction of its data. Now: let´s say a user recognizes an error in data A within system B. In order to maintain the data constistency and source of truth, that user is not allowed to change data A in system B, but he needs to change it in service A because service A is the master for data A. In such an architecture: why would you need a dedicated MDM. What do you think?

Question: what is the benefit of implementing a microservice (uS) infrastructure plus having a huge MDM system on top/in parallel? If the different uS do hold all relevant data and do own that data by the sense of being really responsible and the "master"-system for that data, then there is no point in having that data within a MDM software on top.

Example: service A is the only responsible system for data A and is caring about distributing that data A to any system in need of A. Service A could be a uS with a RESTful HA abstraction of its data. Now: let´s say a user recognizes an error in data A within system B. In order to maintain the data consistency and source of truth, that user is not allowed to change data A in system B, but he needs to change it in service A because service A is the master for data A. In such an architecture: why would you need a dedicated MDM. What do you think?