Tag Archives: Data Integration Platform
On November 10, Informatica made history with the launch of Informatica 9. In my mind, being a SOA enthusiast, another equally significant event transpired – the birth of SOA-based Data Services – transformational SOA data integration that can revive your enterprise architecture.
So, what exactly are SOA-based Data Services and why am I so excited?
Being information driven is as much an organizational commitment as it is a technology commitment. The following outlines the major components required to be information driven.
Data Governance (DG) – DG is the overarching program for a data driven company. In my last blog, I defined DG as the practice of managing data as a corporate asset across the enterprise. It involves the processes, policies, standards, organization, and technologies required to manage and ensure the availability, accessibility, quality, consistency, auditability, and security of data in a company or institution.
Who should own DG? In most things we do, we look for the single point of accountability. In this instance, I recommend a collective structure of senior business managers who are accountable for the data subjects that drive your business. Additionally, I suggest a senior member of IT who can drive change across IT systems. (more…)
This week, we announced the acquisition of AddressDoctor, the market leader of global address validation with coverage for over 200 countries and territories. This is another example of how we are continually working to deliver the most advanced data quality products to our customers. Address Doctor provides an address validation engine which is already fully integrated into Informatica Data Quality. This acquisition is simply another step towards market leadership for Informatica in the enterprise data quality market. Rob Karel from Forrester referred to our vision of pervasive data quality – supporting all roles, all applications, all data domains and all stages of the data integration lifecycle in his blog.
Let’s focus on “all data domains” and how the AddressDoctor acquisition supports this key criteria for successful enterprise data quality. (more…)
As I discussed before, it’s not enough to walk through a functional checklist for a data integration platform. It’s important to make sure that it works in the right way. In my last posting, I discussed the concept of a “unified” platform and its implications for the user experience.
The second key aspect of how a data integration platform works is its openness—how much it is designed to work with the broader IT environment. Data integration, by definition, touches a large portion of the IT environment, which could mean thousands of different applications and data sources in large organizations. Moreover, it’s not just the systems inside the firewall you need to be concerned with.
In most cases, it’s important to also support integration with the systems of B2B partners such as customers, suppliers, distributors, etc., as well as any SaaS partners. And the platform has to support any technology standard such as those for operating systems or databases which have been instituted. Frankly, there’s not much use in a data integration platform that isn’t designed to work with as broad a range of applications and systems as possible. (more…)
If you say the words “data integration“, different people may think of different things. Some think of ETL (extract-transform-load) tools. Others think of enterprise application integration (EAI) technologies or message brokers. But in most cases, regardless of which tool leaps to mind, people think about how data is integrated inside of an organization, or enterprise data integration.
In other words, how data is shared between different applications and systems inside the firewall. But this is just one aspect or realm within the broader data integration discipline, albeit an important one and generally the one most people start with.
Technology vendors like to talk about platforms, because platforms imply a broader footprint both in terms of functional capabilities and in terms of implementation usage. Platforms also sound more “strategic,” even if the practical implications are vague. But the term “platform” can also be simple marketing hype. How do you know when a software “platform” is really a platform? More specifically, do data integration platforms exist now?