When people talk about operational data integration, they are typically referring to migrating and loading small quantities of data (usually individual records or transactions) moments after the data is created. An example of this is when a customer updates his or her address on a website and within seconds all of the other operational systems within the company that owns the site have access to that updated information.
Unfortunately, many organizations implement analytical data integration and operational data integration as completely separate and autonomous islands. The problem with this approach is that there is no mechanism to ensure that the actual logic or rules involved in integrating multiple data sources is consistent across these two different islands. The disparity of integration rules and logic is inevitable because the development teams are typically different people in different groups.
One of the strengths of a successful master data management (MDM) program is to establish a centralized repository, or hub, that will store and maintain the integration logic required to integrate data from multiple systems. The MDM hub provides operational access to subject-area information based on the various contributing operational systems.
Dig Deeper on Enterprise data integration (EDI) software
Related Q&A from Evan Levy
Learn the difference between change data capture (CDC) and data federation. Find out how companies can use both data integration technologies to ... Continue Reading
With Software-as-a-Service (SaaS) applications growing in popularity, learn about the SaaS data integration challenges companies should be aware of ... Continue Reading
Find out if real-time data integration applications has more data quality issues than other approaches. Also, see if real-time or near-real-time ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.