Skip to main content

Governance Applications - Hybrid Deployment

Talend Data Stewardship and Talend Data Preparation can be deployed in a hybrid mode so that data is not required to flow to Talend Cloud. The following diagram illustrates how Talend recommends these components be deployed to:
  1. Ensure high availability.
  2. Allow one TDS / TDP environment to be accessed via the Talend Cloud application switcher.
  3. Use Talend Cloud for user management and security (mandatory).
  4. Leverage IaaS services for non-Talend components of the architecture - Shared file system, Kafka / ZooKeeper, MongoDB and a Load Balancer.
Talend Cloud Talend Data Stewardship and Talend Data Preparation hybrid mode diagram.

Putting this configuration into the wider context, we can see a modified version of the Pre-Production / Production environment from the 'Data Fabric' section, with the addition of the hybrid TDS / TDP applications:

Talend Cloud Real-Time Big Data pre-production and production with TDS and TDP hybrid diagram.

For Talend Data Preparation we also have the option of deploying components that allow Talend Data Preparation to access files on a Big Data Platform and also do the compute of the Preparation on this Big Data Platform. The separation of concerns between the two servers is optional, dependent on the your requirements / restrictions concerning your edge node(s). Note that both the Spark Job Server and the Streams Runner can only be installed on a Linux machine. For more information about running Preparations on a Big Data Cluster, see Talend Data Preparation architecture and Adding a dataset from HDFS.

Talend Cloud Data Preparation hybrid with Big Data diagram.

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!

Leave your feedback here