Talend Integration Cloud (TIC) is a fully-managed cloud option. It provides the great data integration, data quality, and Big Data features from Talend in a cloud environment that is managed, monitored, maintained, and secured by Talend. This article explains the different architecture models supported by Talend Integration Cloud.
This is the first kind of architecture, where Talend Studio is installed locally behind a firewall. Once the design activities are completed, the Jobs are published to the cloud. All the data routing between Studio and the cloud is performed over HTTPS and is very secure.
In this architecture, the integration flows and templates are run in the cloud. The Runtime engines are also in the cloud.
This is the second type of architecture, which is very similar to the SaaS and cloud architecture. However, in this architecture, the runtime engine is behind the firewall - hence it is called a “remote engine”. So here Talend Studio, the remote engine, the apps, and the databases are behind the firewall.
In this architecture, the integration flows and templates are run in this remote engine, and when it comes to the runtime engines that actually perform the execution of these integration workflows, those are in the cloud. Here again the remote engine sends the status and the logs using HTTPS, and also leverages the on-prem apps and databases.
This is the third type of architecture, similar to the previous architecture with respect to Studio and cloud installation. The different is that the remote engine, the runtime engines, the on-prem apps, and the databases all lie within a virtual private cloud.
Here you could run the integration flows and templates in the remote engine in a VPC. The runtime engines would also be in the VPC.
This architecture is an extension of VPC where the logs are redirected to a file and/or log services. The remote engine flows back only the status or approved log data to the Integration Cloud Service; the rest of the logs are redirected to a file on the remote engine or other log service within the virtual private cloud.
In this architecture, you could run the integration flows and templates in the remote engine in the VPC, leveraging both public and private sources.
Note: In all of these architectures, an additional capability that you could leverage is the remote run/debug capability from Studio directly to the remote engine. The remote engine contains a JobServer, so if you need to do a remote run/debug from Studio to the remote engine, you need to configure the remote JobServer details in the Studio preferences to point to the remote engine.
For more information on configuring this capability, see the Remote run configuration (Talend > Run/Debug) page of the Talend Big Data Platform Studio User Guide.