SOA in Action Blog

« Cooperative SOA Reaps Rich Harvest | Main | Airline Turns to a 'Bus' for Real-Time Messaging »

April 30, 2007

When SOA Meets MDM (Master Data Management)

What is this thing called "Master Data Management" that everyone is talking about, and what's the connection with SOA?

MomentumSI's John Kalogirou connects the dots for us, noting that MDM -- data shared across disparate IT systems and groups -- encompasses a wide range of data sources and systems.

Services access information from a data services layer. A data services layer provides an abstraction layer between producers and consumers of data. The data services layer presents consumers with a virtual aggregated view of data from multiple data sources in a consistent and centralized fashion. The layer's interface supports all consumers (human, application, external parties, or business services) while providing agility to data source providers.

A data service layer offers many benefits. Consumers are insulated from complexity, location, and changes in source data systems through abstraction. Providers have the flexibility to change underlying data schemas without impacting consumers through abstraction. Companies can centrally manage, monitor, measure, and report on the enterprise view of the data and metadata.

John observes that the technical intersection of MDM and SOA occurs at the data services layer. However, wjile MDM and SOA share common design principles, they inherently don't mesh. "MDM typically doesn't embrace SOA's 'loose coupling' principle." He adds that "MDM practitioners contemplating supporting today's SOA systems need to become familiar with SOA standards and strive for loose coupling with external systems. Eliminating point-to-point interfaces and replacing them with service-enabled integration minimizes the impact of changes from integration partners and consumers."

Questions to be asked include the following:

- Does the MDM support extensible data types such as XML?
- Can internal, partner, or client services search, identify, and consume the CDM [canonical data model]?
- What is the effort to replace an external service provider?
- Are data quality and conformance services exposed for use by applications or external parties?
- What is the turnaround for changing the functionality of the current MDM system?
- Can the MDM handle near real-time requests for conformance from participating systems?
- Can the MDM exchange metadata with other MDM systems?
- Can the MDM infer context and take action based on the semantics of the information being exchanged?

Posted by joemckendrick in  | Digg This | Add to del.icio.us

Trackback Pings

TrackBack URL for this entry:
http://www.ebizq.net/mt/mt-tb.cgi/1767

Comments Post a comment




Remember Me?

(you may use HTML tags for style)

We ask that you type your code (displayed below) in the text box.This code is an image that cannot be read by a machine. It prevents automated programs from submitting comments.


Code:



ADVERTISEMENT

 

Partners:

Premier Media Partner
Gartner

Association & Media Partners
Technology Evaluation Centers BPM Forum The Open Group
Business Integration eChannel Line Robert Frances Group
BPMS Watch BP Trends Connect IT
GIM OMG