Actually, Talend open studio for MDM product includes both TOS DI and TOS MDM bundles.
The DI integration perspective in Talend open studio MDM is as same as Talend Open studio Data Integration product.
<item> Grand father item
<item> Father Item
<item> Child Item
I am just looking up Talend in general. I was wondering what would be the deciding factors between me starting to use MDM or the Data Integration (Open Studio).
This is an exploration at the moment - I do have a project on which to work, however it is difficult for me at this point to know the full scope of use for Talend. From what I have read so far, the DI is amply sufficient for my current use. However, am I right if I say that MDM has a larger scope, and that on the long run I might be better off starting with MDM? Are there jobs that only DI will perform, or am I right in seeing DI as kind of a subset of MDM? If that is the case, I think I would probably start with MDM right away.
ANy thoughts/advices on this very welcomed,
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Create systems and workflow to manage clean data ingestion and data transformation.
Introduction to Talend Open Studio for Data Integration.
Test drive Talend's enterprise products.