Contents
What is a master data management platform?
Master Data Management (MDM) is a business-led program for ensuring that the organization’s shared data–aka master data–is consistent and accurate. Master Data Management programs include the people, processes, and systems used to keep master data accurate and consistent.
Is master data management part of data governance?
Master Data Management includes processes from the creation of master data thru to its disposal. Data Governance creates the rules and adjudication of the operational processes that are executed within those processes. Rules do not just start and stop with the MDM application: “Those rules go with the data.
What is the difference between data management and data governance?
Data Governance: The Difference Explained. In the simplest terms, data governance establishes policies and procedures around data, while data management enacts those policies and procedures to compile and use that data for decision-making.
Is MDM and MDG same?
MDM offers robust data integration and distribution capabilities across SAP and non-SAP platforms. MDG is an add-on component of SAP and it can share the same SAP-ERP server providing centralized data. It has limited integration capabilities with non-SAP systems.
Is it possible to combine microservices and master data management?
Combining a microservice ecosystem with master data management is a somewhat controversial idea. They are fundamentally incompatible at first glance. A microservices architecture by definition works autonomously, and linking it with shared master data undermines that independence.
Which is a best practice in microservices architecture?
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?
What are the pros and cons of microservices?
Have the master data hosted as a seperate microservice: Pros: Single source of master data. Cons: Hit on performance since it always a service call over the wire when a lookup happens.
When do you need strong consistency guarantees for microservices?
When you need strong consistency guarantees, one service may represent the source of truth for a given entity, which is exposed through an API. Other services might hold their own copy of the data, or a subset of the data, that is eventually consistent with the master data but not considered the source of truth.