Skip to main content

Talend ESB functional architecture

Talend Studio functional architecture is an architectural model that identifies Talend Studio functions, interactions and corresponding IT needs. The overall architecture has been described by isolating specific functionalities in different functional blocks.

The following chart illustrates the main architectural functional blocks used to handle your enterprise integration tasks.

Talend ESB functional architecture

Five different types of functional block are defined:

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

    From Talend Studio, you can carry out data integration or data service processes, mediation routes and services, and publish them on the Artifact Repository. Talend Studio allows the user (such as a project manager, a developer, or an administrator) to work on any project for which he has authorization to create Web, REST and data services, and mediation routes. For more information on Services or Routes, see their respective chapters of the present user guide.

    From the Web browser, end-users connect to the remotely based Administration Center through a secured HTTP protocol.

  • The Talend Server block includes a web-based Administration Center (application server) with two shared repositories: one based on a Git server and one based on an Artifact repository. Talend Administration Center is also connected to databases: one for administration metadata, one for audit information, and one for activity monitoring. And finally, Talend Administration Center is connected to Talend Runtimes execution server(s).

    The Administration Center enables you to set up the execution of the tasks that handle routes or services execution into the Talend Runtime. Through the Administration Center, you can access and manage the Routes or Services created from Talend Studio and published into the Artifact Repository, and set up and monitor their deployment and execution into the Talend Runtime. For more information, see Executing Jobs, Routes, and Services.

  • The Repositories block represents the Git server and the Talend Artifact Repository. The Git server is used to centralize all project metadata like Jobs, Routines, Routes, Services, shared between the different end-users, and accessible from the Talend Studio to develop them and from the Talend Administration Center to publish, deploy and monitor them. The Talend Artifact Repository is used to store all the Routes and Services that are published from Talend Studio and are ready to be deployed in Talend Runtime.

  • The Talend Execution Servers block represents one or more Talend Runtimes (execution container) deployed inside your information system. The Talend Runtime deploys and executes the routes and services retrieved from the Artifact Repository according to the set up defined in the Administration Center via the web application. For more information on how to manage deployment, see Executing Jobs, Routes, and Services and for more information about Talend Runtime itself, see Introduction to Talend ESB Infrastructure Services.

    If you have several Talend Runtimes on which to deploy the Service and Route artifacts, you will be able to load balance their execution according to your needs. All instances of Talend Runtime will communicate between each other via the Service Locator to identify the one more likely to deploy and execute the artifact(s) set to deployment in Talend Administration Center. The Talend Runtime elected for the deployment will request for the artifact(s) to deploy and execute from the Artifact Repository and the Artifact Repository will thus send the artifact(s) requested along with all the dependencies needed for its/their execution to the Talend Runtime, Talend Runtime that will deploy and execute them.

  • The Databases block represents the Administration, the Audit and the Monitoring databases. The Administration database is used to manage user accounts, access rights and project authorization, and so on. The Audit database is used to evaluate different aspects of the Jobs implemented in projects realized in Talend Studio with the aim of providing solid quantitative and qualitative factors for process-oriented decision support. The Service Activity Monitoring database allows the end-users to monitor service calls. It provides monitoring and consolidated event information that the end-user can use to understand the underlying requests and replies that compose the event, monitor faults that may be unexpectedly generated and support the system management decisions.

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!