Overview

Guidance on set up for state management components

Dapr integrates with existing databases to provide apps with state management capabilities for CRUD operations, transactions and more. It also supports the configuration of multiple, named, state store components per application.

State stores are extensible and can be found in the components-contrib repo.

A state store in Dapr is described using a Component file:

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Component
  3. metadata:
  4.   name: statestore
  5.   namespace: default
  6. spec:
  7.   type: state.<DATABASE>
  8.   version: v1
  9.   metadata:
  10.   - name: <KEY>
  11.     value: <VALUE>
  12.   - name: <KEY>
  13.     value: <VALUE>
  14. ...

The type of database is determined by the type field, and things like connection strings and other metadata are put in the .metadata section. Even though metadata values can contain secrets in plain text, it is recommended you use a secret store.

Visit this guide on how to configure a state store component.

Related topics

Last modified March 18, 2021: Merge pull request #1321 from dapr/aacrawfi/logos (9a399d5)