RethinkDB binding spec

Detailed documentation on the RethinkDB binding component

Component format

The RethinkDB state store supports transactions which means it can be used to support Dapr actors. Dapr persists only the actor’s current state which doesn’t allow the users to track how actor’s state may have changed over time.

To enable users to track change of the state of actors, this binding leverages RethinkDB’s built-in capability to monitor RethinkDB table and event on change with both the old and new state. This binding creates a subscription on the Dapr state table and streams these changes using the Dapr input binding interface.

To setup RethinkDB statechange binding create a component of type bindings.rethinkdb.statechange. See this guide on how to create and apply a binding configuration.

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Component
  3. metadata:
  4. name: changes
  5. spec:
  6. type: bindings.rethinkdb.statechange
  7. version: v1
  8. metadata:
  9. - name: address
  10. value: <REPLACE-RETHINKDB-ADDRESS> # Required, e.g. 127.0.0.1:28015 or rethinkdb.default.svc.cluster.local:28015).
  11. - name: database
  12. value: <REPLACE-RETHINKDB-DB-NAME> # Required, e.g. dapr (alpha-numerics only)

Spec metadata fields

FieldRequiredBinding supportDetailsExample
addressYInputAddress of RethinkDB server“27.0.0.1:28015”, “rethinkdb.default.svc.cluster.local:28015”
databaseYInputRethinDB database name“dapr”

Binding support

This component only supports input binding interface.

Related links

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