Talend Dynamic Engine
New features
| Feature | Description |
|---|---|
| Dynamic Engine v0.24.0 | Dynamic Engine
v0.24.0 introduces multiple security, reliability, and scalability improvements.
Its support for Data Services and Routes is now generally available.
Prerequisites before upgrading:
For the full changelogs and further improvements, see Dynamic Engine v0.24.0 release. |
| Support for Data services and Routes |
Data service and Route tasks are now supported by Dynamic Engines. Only Microservice artifacts are supported by Dynamic Engines. To deploy Data services and Routes in a Dynamic Engine environment, you must install a Dynamic Engine and its environment using Helm. For more information, see Managing Data service and Route tasks in a Dynamic Engine environment. |
| Updating Data service and Route tasks deployed in Dynamic Engine environment |
You can update Data service and Route tasks deployed in a Dynamic Engine environment without downtime. For more information, see Updating Data service and Route tasks. |
Known limitations
Azure File shares billing for logs:
When Dynamic Engine is deployed on Azure and uses Azure file shares as persistent storage, you may see increased costs on your Azure bill. Azure charges based on the number of API calls. The Dynamic Engine services generate frequent directory-listing calls for logs when interacting with the storage, which can significantly increase the number of API calls.
| Impact scope | Workaround |
|---|---|
| All Dynamic Engine versions | Review your Azure storage usage and costs and deactivate the logs as explained in:
|