Skip to main content

Talend MDM functional architecture

Talend MDM architecture can be broken down into functional blocks that enable interaction between users and the MDM Hub and their corresponding IT needs.

The chart below illustrates the main building blocks of Talend MDM.

Information noteNote: The building blocks you have available for use depend on your license and on which edition of MDM you have.

The list below describes the main building blocks of Talend MDM:

  • The Clients block includes one or more Talend Studio(s) and Web browsers that could be on the same or on different machines.

    From the Studio, administrators can set up and operate a centralized master data repository. They can build data models that employ the necessary business and data rules to create a single master copy of the master data. This master data will be propagated back to target and source systems.

    Users of Talend Studio can set the governance rules that include who can read, create, update, and delete data; which validity models are required for data; which privacy policies are enforced; and which recovery provisions are required, to name a few.

    For more information about available administration tasks, see MDM working principles, Stored Procedures, and Security principle in.

    From the Web browser, business users and data stewards can search, display or edit master data handled by the Studio.

    Users of Talend MDM Web UI can carry out any manual interventions necessary to make sure that the master data is clean, consistent, and accurate. Talend MDM Web UI also gives access to Talend Data Stewardship that will allow the dedicated user to manually resolve data issues that results from the matching and integration operations on the master data.

  • The Talend Servers block includes an MDM server - where the master data is governed and monitored.

  • The Databases block includes the MDM database - where the master data is stored.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!