Getting Started

Azure Table Persistence

NuGet Package: NServiceBus.Persistence.AzureTable (5.x)
Target Version: NServiceBus 8.x

Certain features of NServiceBus require persistence to permanently store data. Among them are subscription storage, sagas, and outbox. Various storage options are available including Azure Table and Azure Cosmos DB Table API.

Azure Table Persistence stores NServiceBus data in Azure Table storage or Azure Cosmos DB using the Table API.

Persistence at a glance

For a description of each feature, see the persistence at a glance legend.

Supported storage typesSagas, Outbox, Subscriptions
TransactionsUsing TransactionalBatch, with caveats
Concurrency controlOptimistic concurrency
Scripted deploymentNot supported
InstallersSupported. Subscription, the default table or saga tables derived by convention when no default table is set are created at runtime, when enabled.

Enable Azure Table Persistence

First add a reference to the assembly that contains the Azure Table persistence, which is done by adding a NuGet package reference to NServiceBus.Persistence.AzureTable.

var persistence = endpointConfiguration.UsePersistence<AzureTablePersistence>();

Provisioned throughput rate-limiting with Azure Cosmos DB

When using the provisioned throughput feature, it is possible for the CosmosDB service to rate-limit usage, resulting in "request rate too large" RequestFailedExceptions indicated by a 429 status code.

When using the Azure Table persistence with the outbox enabled, "request rate too large" errors may result in handler re-execution and/or duplicate message dispatches depending on which operation is throttled.
Microsoft provides guidance on how to monitor request rate usage.

The Azure.Data.Tables SDK handles these exceptions by automatically retrying the failed request based on headers included in the response. The retry policy can be adjusted through TableClientOptions when initializing the TableServiceClient.

Saga concurrency

When simultaneously handling messages, conflicts may occur. See below for examples of the exceptions which are thrown. Saga concurrency explains how these conflicts are handled, and contains guidance for high-load scenarios.

Starting, updating or deleting saga data

Azure Table Persistence uses optimistic concurrency control when updating or deleting saga data.

Example exception:

Azure.Data.Tables.TableTransactionFailedException: The update condition specified in the request was not satisfied.
Status: 412 (Precondition Failed)
ErrorCode: UpdateConditionNotSatisfied

Supported saga properties' types

Azure Table Persistence supports the same set of types as Azure Table Storage and additional types that can be serialized into JSON using Json.NET. When a saga containing a property of an unsupported type is persisted, an exception containing the following information is thrown: The property type 'the_property_name' is not supported on Azure Table Storage and it cannot be serialized with JSON.NET.


Saga data serialization can be configured by providing a custom JsonSerializerSettings instance:

var persistence = endpointConfiguration.UsePersistence<AzureTablePersistence, StorageType.Sagas>();

persistence.JsonSettings(new JsonSerializerSettings
    Converters =
            new IsoDateTimeConverter
                DateTimeStyles = DateTimeStyles.RoundtripKind

or with a custom JsonReader instance:

var persistence = endpointConfiguration.UsePersistence<AzureTablePersistence, StorageType.Sagas>();

    readerCreator: textReader =>
        return new JsonTextReader(textReader);

or with a custom JsonWriter instance:

var persistence = endpointConfiguration.UsePersistence<AzureTablePersistence, StorageType.Sagas>();

    writerCreator: writer =>
        return new JsonTextWriter(writer)
            Formatting = Formatting.None

Saga Correlation property restrictions

Saga correlation property values are subject to the underlying Azure Storage table PartitionKey and RowKey restrictions:


Related Articles

Last modified