| title | description | services | author | manager | keywords | ms.service | ms.devlang | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|
Task hubs in Durable Functions - Azure |
Learn what a task hub is in the Durable Functions extension for Azure Functions. Learn how to configure configure task hubs. |
functions |
cgillum |
jeconnoc |
azure-functions |
multiple |
conceptual |
09/29/2017 |
azfuncdf |
A task hub in Durable Functions is a logical container for Azure Storage resources that are used for orchestrations. Orchestrator and activity functions can only interact with each other when they belong to the same task hub.
Each function app has a separate task hub. If multiple function apps share a storage account, the storage account contains multiple task hubs. The following diagram illustrates one task hub per function app in shared and dedicated storage accounts.
A task hub consists of the following storage resources:
- One or more control queues.
- One work-item queue.
- One history table.
- One instances table.
- One storage container containing one or more lease blobs.
All of these resources are created automatically in the default Azure Storage account when orchestrator or activity functions run or are scheduled to run. The Performance and Scale article explains how these resources are used.
Task hubs are identified by a name that is declared in the host.json file, as shown in the following example:
{
"durableTask": {
"HubName": "MyTaskHub"
}
}Task hub names must start with a letter and consist of only letters and numbers. If not specified, the default name is DurableFunctionsHub.
Note
The name is what differentiates one task hub from another when there are multiple task hubs in a shared storage account. If you have multiple function apps sharing a shared storage account, you have to configure different names for each task hub in the host.json files.
[!div class="nextstepaction"] Learn how to handle versioning