Mastering Data Management

More in Business Process Management

• New ebook: Understanding Big Data
• 37 Definitions of “Employee ID”
• Defining Terms: Agree, or Doom your Project
• Establishing a Valid Business “Need to Know” for Sensitive Data

More in MDM

• Best Practices in Test Data Management: Discovering and Subsetting
• TDWI Chicago Preview: Data Warehousing, Analytics & More
• Who’s Afraid of the Big Bad Data?
• MDM for Chief Privacy Officers: A healthcare provider example

More from Marty Moseley

• IAIDQ Blog Carnival: Data Fitness & Garbage
• Mind the Gap and Do Data Governance Better
• Measuring Data Governance: Metrics that Matter
• Measuring Data Governance: How Do You Know You’ve Made a Difference?

Share this Post

Recent Comments

• ICMCC News Page » Where East Meets West: ehealth in China and the US on Where East Meets West: ehealth in China and the US
• Kim’s Training Podcast on Training as a Safety Net: Kim May
• TDWI Chicago Preview: Data Warehousing, Analytics & More | Mastering Data Management on New ebook: Understanding Big Data

A hybrid MDM model blends aspects of the registry and centralized models.

Continuing our survey of multidomain MDM and the supporting architectures, today’s post is focused on the hybrid architectural model.

A hybrid model copies the detailed data about complex objects from source systems into containers. The major benefit of the hybrid model is faster performance, because complex objects already have all of the data they need to satisfy a request under their control.

This capability eliminates the need for a hybrid system to federate data from external sources, which positively impacts performance and availability.

One drawback of the hybrid approach, caused by data redundancy, occurs when updates or changes need to be made to master data. Redundancy not only means more work and higher maintenance costs, but it also introduces more risk of errors occurring and of data values getting out of sync.

Another drawback of the hybrid approach occurs because changes in attribute characteristics, relationships, semantics, processing or structural rules have to be coordinated between the composite object and outlying source systems.

Thus, the hybrid approach tends to be more invasive. However, depending on an organization’s business requirements, the higher performance or lower latency demands of a hybrid approach will usually outweigh the redundancy and maintenance costs, along with additional risk factors.

Organizations that thrive on real-time access to data with less tolerance for latency will pick a hybrid approach over the slower registry model.

However, there’s still one more model to consider: the centralized model.

This post is part of Marty Moseley's Multidomain MDM Series. View the table of contents for links to any parts you may have missed.