A user asked me this question the other day and I thought it was worth posting. Of course, there are probably a few good reasons. The chief of which might have been that Informatica was not aware of the availability of the Open Source Software based MDM application from Talend. But there are other conditions that might have applied:
- Lack of awareness – the OSS MDM application is brand new, even though the source code from whence it came, is not to young (Amalto, a small French vendor).
- Not comprehensive – the Amalto MDM application had no proven track records across all the different vectors of complexity (industry, data domain, use case, implementation style, organization model). Functionality seemed (in 2009) to focus on: broad number of but generally less complex definition of master data objects.
- Unproven – I estimated Amalto had no more than 8 MDM customers by the spring 2009. It was reported that Amalto had 6 customer of MDM in 2007 also. This is not exactly signs of a world beating MDM solution.
- Technology differences – Amalto had sported an XML database; this is not a common approach, certainly in MDM land, and might not necessarily have been consistent with how Informatica wants to deliver data stores to its clients. But, this might lead to one of the more interesting aspects of an OSS based MDM offering… Also, Amalto’s MDM offering was itself built on several OSS components.
Bottom line: Amalto’s MDM product was oriented around the technical side of MDM; its technology was flexible, agile, and effective at modeling all kinds of interesting master data problems, and could be part of a mature SOA based infrastructure. Its challenge was more on the “solution” side, that being, knowledge of the MDM discipline, governance, process, and organization – many of the other pieces needed within the overall program. As such, it seems to be a better fit as a kernel for another MDM “solution” – much as Talend would want it to be viewed.