Environments and deployment strategy - 7.3

Talend Physical Reference Architecture

English (United States)
Talend Data Fabric
Talend Data Preparation
Talend Data Stewardship
Talend Studio
Installation and Upgrade
Reference Architecture

This section focuses on the Environment Strategy for an Enterprise deployment of Talend. Typically an Enterprise deployment of Talend will include:

  • Multiple user personas, each with tools suited to their requirements, such as Data Preparation for a business user, or Talend Studio for a data engineer
  • Artifacts developed in Talend Studio requiring a full Enterprise Software Development Life Cycle (SDLC), including Continuous Integration and Continous Delivery (CI/CD)
  • Multiple teams working on multiple projects in parallel
  • High Availability and Load Balancing
  • Environment specific security / access

For Enterprise deployments, Talend recommends a four environment strategy, coupled with an automated approach to building / testing and deployment:

Environment Strategy

A typical Enterprise deployment of Talend should have four environments: development, test, pre-production and production.

Development: The environment where developers build and unit test their artifacts.

Test: Integration testing and ensuring that no dependencies to the development environment have been left in by accident - it should not include high availability so testing can focus on testing the logic rather than environment testing.

Pre-Production: An environment that should be as close a mirror of production as possible - used for high availability testing, production patch testing, performance testing and user acceptance testing.

Production: The production environment.