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-azure-storage-provider.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -237,6 +237,7 @@ You can enable extended sessions by setting `durableTask/extendedSessionsEnabled
237
237
}
238
238
}
239
239
```
240
+
---
240
241
241
242
There are two potential downsides of this setting to be aware of:
242
243
@@ -288,8 +289,6 @@ If you are not seeing the throughput numbers you expect and your CPU and memory
288
289
### Flex Consumption Plan
289
290
The [Flex Consumption plan](../flex-consumption-plan.md) is an Azure Functions hosting plan that provides many of the benefits of the Consumption plan, including a serverless billing model, while also adding useful features, such as private networking, instance memory size selection, and full support for managed identity authentication.
290
291
291
-
Azure Storage is currently the only supported [storage provider](durable-functions-storage-providers.md) for Durable Functions when hosted in the Flex Consumption plan.
292
-
293
292
You should follow these performance recommendations when hosting Durable Functions in the Flex Consumption plan:
294
293
295
294
* Set the [always ready instance count](../flex-consumption-how-to.md#set-always-ready-instance-counts) for the `durable` group to `1`. This ensures that there is always one instance ready to handle Durable Functions related requests, thus reducing the application's cold start.
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/durable-functions-storage-providers.md
+4-9Lines changed: 4 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ The source code for the DTFx components of the Azure Storage storage provider ca
54
54
55
55
## <aname="netherite"></a>Netherite
56
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).
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-of-support announcement](https://azure.microsoft.com/updates/?id=489009).
58
58
59
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.
60
60
@@ -128,7 +128,6 @@ If no storage provider is explicitly configured in host.json, the Azure Storage
128
128
See the [durable task scheduler getting started documentation](./durable-task-scheduler/quickstart-durable-task-scheduler.md).
129
129
130
130
### Configuring the MSSQL storage provider
131
-
132
131
Enabling the MSSQL storage provider requires a configuration change in your `host.json`. For C# users, it also requires an additional installation step.
133
132
134
133
#### `host.json` Configuration
@@ -149,25 +148,21 @@ The following example shows the minimum configuration required to enable the MSS
149
148
}
150
149
```
151
150
152
-
For more detailed setup instructions, see the [MSSQL provider's getting started documentation](https://microsoft.github.io/durabletask-mssql/#/quickstart).
151
+
For more detailed setup instructions, see the [MSSQL provider's getting started documentation](./quickstart-mssql.md) and [documentation on github.io](https://microsoft.github.io/durabletask-mssql/#/quickstart).
153
152
154
153
#### Install the Durable Task MSSQL extension (.NET only)
155
154
156
155
> [!NOTE]
157
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.
158
157
159
-
You'll need to install the latest version of the MSSQL storage provider Extension on NuGet. This usually means including a reference to it in your `.csproj` file and building the project.
160
-
161
-
The Extension package to install depends on the .NET worker you are using:
162
-
- For the _in-process_ .NET worker, install [`Microsoft.DurableTask.SqlServer.AzureFunctions`](https://www.nuget.org/packages/Microsoft.DurableTask.SqlServer.AzureFunctions).
163
-
- For the _isolated_ .NET worker, install [`Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer`](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer).
158
+
You'll need to install the latest version of the MSSQL storage provider Extension on NuGet: [`Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer`](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer). This usually means including a reference to it in your `.csproj` file and building the project.
164
159
165
160
## Comparing storage providers
166
161
167
162
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.
168
163
169
164
> [!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).
165
+
> 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-of-support announcement](https://azure.microsoft.com/updates/?id=489009).
0 commit comments