In-memory
Detailed documentation on the in-memory state component
The in-memory state store component maintains state in the Dapr sidecar’s memory. 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
To setup in-memory state store, create a component of type state.in-memory
. See this guide on how to create and apply a state store configuration.
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
spec:
type: state.in-memory
version: v1
metadata:
# Uncomment this if you wish to use In-memory as a state store for actors (optional)
#- name: actorStateStore
# value: "true"
Note: While in-memory does not require any specific metadata for the component to work,
spec.metadata
is a required field.
Related links
- Basic schema for a Dapr component
- Learn how to create and configure state store components
- Read more about the state management building block
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified December 18, 2024: Merge pull request #4461 from dapr/dependabot/npm_and_yarn/daprdocs/nanoid-3.3.8 (5660a64)