Microservices and "Master Data Management" - are they compatibile?

by Andy   Last Updated November 08, 2018 22:05 PM

My understanding is that separate data store per service is a best practice in microservices architecture. This Nginx article mentions that, but it goes on to advocate a Master Data Management system for ensuring consistency of data across disparate data stores. How can both coexist peacefully? It seems to me that each individual service would be competing with the MDM solution for "owning" the rights to create/update/master data.

I'd love to hear from anyone that has an MDM solution plus separate data store per service. What MDM tool(s) are you using? Doesn't each service "master" its own data - e.g., shouldn't Order data be written ONLY via the Order microservice? If the MDM solution detects a problem with regard to data consistency around Order data, does it instruct the Order service to reconcile it - or does this happen in the MDM tool?

Also, how do you stand up an MDM solution without introducing undesirable coupling between services and the MDM solution? Teams developing services should be able to change schema as needed, but an MDM solution would need to know the intimate details of schema and thus be tightly coupled right?

Tags : microservices

Related Questions

Should a microservice expose only one public API?

Updated September 11, 2016 09:02 AM