Skip to main content

Data Management Platform


The rest of this document contains the Physical Reference Architecture diagrams for each of the Talend on-premise platforms. Talend Data Fabric is a single, unified platform with features that are enabled by your licensing level. Some of these features have additional infrastructure requirements, but all platforms share the core Data Management components.

Talend Data Management Platform provides customers with Data Integration and Data Quality capabilities, which can be executed with a batch architectural style of data processing.

For details about the function of each Talend component on the diagrams and a logical architecture diagram, please see:


Points of note:

  • In each development environment in this guide you will find a full CI/CD stack. A subset of this same stack is shown in all other environments - minus the components need to create, compile and unit test Talend artifacts as this only occurs in the development environment.
  • There is no high availability at the application level in the development and test environments.
  • You can add as many Jobservers as required - for example you could have one Jobserver per line of business or project if required.


Pre-Production / Production

Points of note:

  • TAC high availability is primarily to ensure that there is always a scheduler (quartz) available to instantiate tasks as required. The quartz cluster is active - active so any TAC node could potentially instantiate a job as per the schedule.
  • However, this should not be confused with High Availability of the TAC web application, which must not be active - active, hence why a failover device is shown and not a load balancer. You must only use one TAC node at any given time. The primary use case for the failover device is if you use a third party scheduler to trigger jobs via the TAC metaservlet (API).
  • For more information on high availability of TAC and jobserver, please see:

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 – let us know how we can improve!