The durable task scheduler is a solution for durable execution in Azure. Durable execution is a fault-tolerant approach to running code that handles failures and interruptions through automatic retries and state persistence. Scenarios where durable execution is required include distributed transactions, multi-agent orchestration, data processing, infrastructure management, and others. Coupled with a developer orchestration framework like Durable Functions or the Durable Task SDKs, the durable task scheduler enables developers to author stateful apps that run on any compute environment without the need to architect for fault tolerance.
Developers can use the durable task scheduler with the following orchestration frameworks:
- Durable Functions
- Durable Task SDKs, also referred to as "portable SDKs"
- Durable Task Framework
When used with Durable Functions, a feature of Azure Functions, the durable task scheduler plays the role the "backend provider", where state data is persisted as the app runs. While other backend providers are supported, only the durable task scheduler offers a fully managed experience, which removes operational overhead from users. Additionally, the scheduler offers exceptional performance, reliability, and the ease of monitoring orchestrations.
The durable task scheduler plays a similar role in the Durable Task Framework as in Durable Functions.
The Durable Task SDKs provide a lightweight client library for the durable task scheduler. When running orchestrations, apps using these SDKs would make a connection to the scheduler's orchestration engine in Azure. These SDKs are called "portable" because apps that leverage them can be hosted in various compute environments, such as Azure Container Apps, Azure Kubernetes Service, Azure App Service, or VMs.
For more information on how to use the Azure Functions durable task scheduler and to explore its features, please refer to the official documentation
This repo contains samples in different directories for all orchestration frameworks supported by the durable task scheduler. The following table provides some considerations when choosing a framework.
| Consideration | Durable Task SDKs | Durable Functions | Durable Task Framework |
|---|---|---|---|
| Hosting option | Azure Container Apps, Azure Kubernetes Service, Azure App Service, VMs | Azure Functions | Azure Container Apps, Azure Kubernetes Service, Azure App Service, VMs |
| Language support | .NET, Python, Java (coming soon), JavaScript (coming soon) | .NET, Python, Java, JavaScript, PowerShell | .NET |
| Official support | No | Yes | No |
| Durable task scheduler emulator | Available | Available | Available |
| Monitoring dashboard | Available | Available 1 | Available 1 |
| Durable Entities | Not supported | Supported | Not supported |
| Other supported feature(s) | Scheduler | Supports all backend providers |
1 The out-of-the-box monitoring dashboard is available only when using the durable task scheduler as the backend provider.
Note: For all new apps, we recommend the portable SDKs over the Durable Task Framework as the former follows more modern .NET conventions and will be the focus of our future investments.
Durable Task SDKs
Durable Functions
Your feedback is essential in shaping the future direction of this product. We encourage you to share your experiences, both the good and the bad. If there are any missing features or capabilities that you would like to see supported in the Durable Task Scheduler, we want to hear about them.
Note: This is an early-stage version of the product. You can share your feedback either by dropping us an issue in this repo (other private preview users will see your issue) or send an email to our product managers Nick and Lily ([email protected]; [email protected]).
![microsoft-github-operations[bot]](https://avatars.githubusercontent.com/in/41902?v=4){kind=small}
