RethinkDB

To setup RethinkDB state store, create a component of type . See the how-to guide to create and apply a state store configuration.

Warning

The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets, as described here.

RethinkDB state store supports transactions, so it can be used to persist Dapr Actor state. By default, the state will be stored in table named daprstate in the specified database.

Additionally, if the optional archive metadata is set to true, on each state change, the RethinkDB state store will also log state changes with timestamp in the table. This allows for time series analyses of the state managed by Dapr.

To connect to the admin UI: