You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/durable-functions-storage-providers.md
+6-37Lines changed: 6 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,9 @@ The source code for the DTFx components of the Azure Storage storage provider ca
52
52
> [!NOTE]
53
53
> Standard general purpose Azure Storage accounts are required when using the Azure Storage provider. All other storage account types are not supported. We highly recommend using legacy v1 general purpose storage accounts because the newer v2 storage accounts can be more expensive for Durable Functions workloads. For more information on Azure Storage account types, see the [Storage account overview](../../storage/common/storage-account-overview.md) documentation.
54
54
55
-
## <aname="netherite"></a>Netherite
55
+
## <aname="netherite"></a>Netherite
56
+
> [!NOTE]
57
+
> Support for using the Netherite storage backend with Durable Functions will end 31 March 2028. It is recommended that you start evaluating the Durable Task Scheduler for workloads that you're currently using Netherite for. See [end-ofsupport announcement](https://azure.microsoft.com/updates/?id=489009).
56
58
57
59
The Netherite storage backend was designed and developed by [Microsoft Research](https://www.microsoft.com/research). It uses [Azure Event Hubs](../../event-hubs/event-hubs-about.md) and the [FASTER](https://www.microsoft.com/research/project/faster/) database technology on top of [Azure Page Blobs](../../storage/blobs/storage-blob-pageblob-overview.md). The design of Netherite enables higher-throughput processing of orchestrations and entities compared to other providers. In some benchmark scenarios, throughput was shown to increase by more than an order of magnitude when compared to the default Azure Storage provider.
58
60
@@ -125,42 +127,6 @@ If no storage provider is explicitly configured in host.json, the Azure Storage
125
127
### Configuring durable task scheduler (preview)
126
128
See the [durable task scheduler getting started documentation](./durable-task-scheduler/quickstart-durable-task-scheduler.md).
127
129
128
-
### Configuring the Netherite storage provider
129
-
130
-
Enabling the Netherite storage provider requires a configuration change in your `host.json`. For C# users, it also requires an additional installation step.
131
-
132
-
#### `host.json` Configuration
133
-
134
-
The following host.json example shows the minimum configuration required to enable the Netherite storage provider.
135
-
136
-
```json
137
-
{
138
-
"version": "2.0",
139
-
"extensions": {
140
-
"durableTask": {
141
-
"storageProvider": {
142
-
"type": "Netherite",
143
-
"storageConnectionName": "AzureWebJobsStorage",
144
-
"eventHubsConnectionName": "EventHubsConnection"
145
-
}
146
-
}
147
-
}
148
-
}
149
-
```
150
-
151
-
For more detailed setup instructions, see the [Netherite getting started documentation](https://microsoft.github.io/durabletask-netherite/#/?id=getting-started).
152
-
153
-
#### Install the Netherite extension (.NET only)
154
-
155
-
> [!NOTE]
156
-
> If your app uses [Extension Bundles](../functions-bindings-register.md#extension-bundles), you should ignore this section as Extension Bundles removes the need for manual Extension management.
157
-
158
-
You'll need to install the latest version of the Netherite Extension on NuGet. This usually means including a reference to it in your `.csproj` file and building the project.
159
-
160
-
The Extension package to install depends on the .NET worker you are using:
161
-
- For the _in-process_ .NET worker, install [`Microsoft.Azure.DurableTask.Netherite.AzureFunctions`](https://www.nuget.org/packages/Microsoft.Azure.DurableTask.Netherite.AzureFunctions).
162
-
- For the _isolated_ .NET worker, install [`Microsoft.Azure.Functions.Worker.Extensions.DurableTask.Netherite`](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.DurableTask.Netherite).
163
-
164
130
### Configuring the MSSQL storage provider
165
131
166
132
Enabling the MSSQL storage provider requires a configuration change in your `host.json`. For C# users, it also requires an additional installation step.
@@ -200,6 +166,9 @@ The Extension package to install depends on the .NET worker you are using:
200
166
201
167
There are many significant tradeoffs between the various supported storage providers. The following table can be used to help you understand these tradeoffs and decide which storage provider is best for your needs.
202
168
169
+
> [!NOTE]
170
+
> Support for using the Netherite storage backend with Durable Functions will end 31 March 2028. It is recommended that you start evaluating the Durable Task Scheduler for workloads that you're currently using Netherite for. See [end-ofsupport announcement](https://azure.microsoft.com/updates/?id=489009).
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/durable-task-scheduler/choose-orchestration-framework.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.author: azfuncdf
7
7
author: lilyjma
8
8
---
9
9
10
-
# Choosing your orchestration framework
10
+
# Choosing an orchestration framework
11
11
12
12
The goal of this article is to provide information about two developer-oriented orchestration frameworks supported by Azure and considerations for when to choose which. The article will also provide some context around scenarios that warrant the use of an orchestration framework.
description: Learn about the characteristics of the Azure Functions Durable Task Scheduler backend.
3
+
description: Learn about the characteristics of the Azure Functions Durable Task Scheduler.
4
4
ms.topic: conceptual
5
5
ms.date: 04/24/2025
6
6
---
@@ -85,12 +85,14 @@ Aside from monitoring, you can also perform management operations on the dashboa
85
85
Access to the dashboard is secured by identity and role-based access controls.
86
86
87
87
### Multiple task hubs
88
+
> [!TIP]
89
+
> One way to optimize cost when using the Durable Task Scheduler is to create multiple task hubs in the same scheduler instance so that multiple apps or environments can share one resource.
88
90
89
91
State is durably persisted in a *task hub*. A [task hub](../durable-functions-task-hubs.md) is a logical container for orchestration and entity instances and provides a way to partition the state store. With one scheduler instance, you can create multiple task hubs that can be used by different apps. To access a task hub, the caller's identity *must* have the required role-based access control (RBAC) permissions.
90
92
91
-
Creating multiple task hubs isolates different workloads that can be managed independently. For example, you can create a task hub for each environment (dev, test, prod) or for different teams within your organization.
93
+
Creating multiple task hubs isolates different workloads that can be managed independently. For example, you can create a task hub for each environment (dev, test, prod) or for different teams within your organization. You can also have multiple apps share the same scheduler instance by configuring them to use different task hubs in the scheduler. Each task hub gets its own monitoring dashboard and access is isolated and secured by RBAC.
92
94
93
-
Create these task hubs in a single scheduler instance as a way to reduce costs by sharing the same scheduler resources across multiple task hubs. Be aware that task hubs under the same scheduler instance share the same resources, so if one task hub is heavily loaded, it might affect the performance of the other task hubs.
95
+
Scheduler sharing is a great way to optimize cost when multiple teams have scenarios requiring orchestrations. While there is no limit to how many task hubs can be created in one scheduler instance, be aware that task hubs under the same scheduler instance share the same resources, so if one task hub is heavily loaded, it might affect the performance of the other task hubs.
0 commit comments