In-memory

Detailed documentation on the In Memory pubsub component

The in-memory pub/sub component operates within a single Dapr sidecar. This is primarily meant for development purposes. State is not replicated across multiple sidecars and is lost when the Dapr sidecar is restarted.

Component format

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: pubsub
spec:
  type: pubsub.in-memory
  version: v1
  metadata: []

Note: in-memory does not require any specific metadata for the component to work, however spec.metadata is a required field.

Related links

• Basic schema for a Dapr component in the Related links section
• Read this guide for instructions on configuring pub/sub components
• Pub/Sub building block

Last modified March 21, 2024: Merge pull request #4082 from newbe36524/v1.13 (f4b0938)