How to: Manage state with the Dapr State Management .NET SDK

Mon, 01 Jan 0001 00:00:00 +0000

Let’s walk through how to manage state using the Dapr.StateManagement package. We’ll use the sample project provided here for the following demonstration, covering typed state store clients via the source generator, direct client usage for bulk operations and transactions, and optimistic concurrency control with ETags. In this guide, you will:

Deploy a .NET application (StateManagementExample)
Utilize the Dapr .NET State Management SDK to save, retrieve, and delete state entries
Use ETags for optimistic concurrency control
Perform bulk operations and state transactions
Use the source generator to create a strongly-typed, store-scoped interface

In the .NET example project:

DaprStateManagementClient usage

Mon, 01 Jan 0001 00:00:00 +0000

Lifetime management

A DaprStateManagementClient holds long-lived network resources (gRPC channels, HTTP connections). For best performance:

Register a single shared instance and reuse it for the lifetime of the application.
Avoid creating and disposing a client per operation — this can lead to socket exhaustion.
The DI registration via AddDaprStateManagementClient() defaults to ServiceLifetime.Singleton, which is the recommended approach for most applications.

The client is thread-safe and can be shared across concurrent requests.

Dapr State Management .NET SDK on Dapr Docs

How to: Manage state with the Dapr State Management .NET SDK

DaprStateManagementClient usage

Lifetime management