Deployment patterns for Dynamic Engine in an SDLC (Software Development Life Cycle)

Pattern 1: One-to-One (1:1) Dynamic Engine and Environment Deployment

In this pattern, a Dynamic Engine instance is created in Talend Management Console and provisioned on its own Kubernetes cluster. A single Dynamic Engine environment is then associated with each instance. Each engine-environment pair is dedicated to a specific phase of your development life cycle. For example, one pair is for the Development phase, another for the Staging phase, and a third for the Production phase.

This setup is ideal for physically separating execution environments, helping manage security, access control, and scale Kubernetes clusters independently for each environment. You can also promote tasks between environments directly through Talend Management Console.

Pattern 2: One-to-Many (1:N) Dynamic Engine and Environment Deployment

In this pattern, a single Dynamic Engine instance is created in Talend Management Console, with multiple Dynamic Engine environments connected to it. All environments share the same Kubernetes cluster and that single Dynamic Engine instance.

This deployment reduces operational costs while still segregating tasks across different environments, making it suitable for scenarios where physically separate execution environments are unnecessary. Tasks can also be promoted between environments directly through Talend Management Console.