User Client PC

Development

Talend Studio only appears in the Development Environment diagram. Talend does not recommend making changes to logic in any other environment than Development. If changes are required in higher environments, they should be made in the Development environment, published to Talend Cloud and promoted as described in the Environments section. Putting in place a well defined Git workflow that includes Git branching and tagging is strongly recommended. A Git Tag allows the creation of an unchangeable, snapshot copy of the metadata used to build an artifact that is deployed to Talend Cloud. It is strongly recommended that Continuous Integration/Deployment capabilities of Talend are also leveraged.

Talend Studio can be hosted on a local developer machine, VM or via a Desktop-as-a-Service (DaaS) solution (such as AWS Workspaces or Azure Windows Virtual Desktop). For larger scale deployments a DaaS solution is recommended as this makes maintenance and upgrades simpler and generally lowers costs.

The installation and configuration of Talend Studio can be scripted or automated.