# Talend Dynamic Engine

## New features

| Feature | Description |
| --- | --- |
| Dynamic Engine<br>v0.24.0 | Dynamic Engine<br>v0.24.0 introduces multiple security, reliability, and scalability improvements.<br>Its support for Data Services and Routes is now generally available.<br><br>Prerequisites before upgrading:<br><br><ul> <li>All Data Services and Routes that were deployed in versions prior to                           0.24.0 must be undeployed before the upgrade and only redeployed after                           the upgrade is completed. Failing to do so may cause unexpected behavior                           or system failures. <p>Do not use the <span>Redeploy</span>                              button in <span>Talend Management Console</span> for this step. Follow the <a href="https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/undeploying-data-service-and-route-tasks-in-dee" target="_blank">classic procedure</a> to undeploy                              and redeploy Data Services and Routes.</p></li> </ul><br><br>For the full changelogs and further improvements, see [Dynamic Engine v0.24.0 release](https://help.qlik.com/talend/en-US/dynamic-engine-changelog/cloud/dynamic-engine-v0-24-0-release-changelog). |
| 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.<br><br>To deploy Data services and Routes in a Dynamic Engine environment, you must install a Dynamic Engine and its environment using Helm.<br><br>For more information, see [Managing Data service and Route tasks in a<br>Dynamic Engine environment](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/managing-data-services-and-routes-in-dynamic-engine-environments-in-tmc). |
| Updating Data service and Route tasks deployed in Dynamic Engine<br>environment | You can update Data service and Route tasks deployed in a Dynamic Engine environment without downtime.<br><br>For more information, see [Updating Data service and Route<br>tasks](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/updating-data-service-and-route-tasks-in-dee). |

## 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<br>versions | Review your Azure storage usage and costs and deactivate the logs as explained in:<br><br><ul> <li>Helm deployment: <a href="https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/deploy-environment-with-disabled-logs-metrics" target="_blank">Deactivating logs and metrics transfer upon                        deployment or upgrade</a>. </li> <li>Standard Kubectl deployment: <a href="https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/deploy-environment-with-disabled-logs-metrics" target="_blank">Deactivating logs and metrics transfer upon                        deployment or upgrade</a>. </li> </ul> |