State stores

Table captions:

Status: Component certification status

• Alpha
• Beta
• Stable

Since: defines from which Dapr Runtime version, the component is in the current status

Component version: defines the version of the component

The following stores are supported, at various levels, by the Dapr state management building block:

State stores can be used for actors if it supports both transactional operations and etag.

Generic

Component	CRUD	Transactional	ETag	TTL	Actors	Query	Status	Component version	Since runtime version
Aerospike	✅		✅				Alpha	v1	1.0
Apache Cassandra	✅			✅			Beta	v1	1.7
CockroachDB	✅	✅	✅		✅	✅	Beta	v1	1.7
Couchbase	✅		✅				Alpha	v1	1.0
Hashicorp Consul	✅						Alpha	v1	1.0
Hazelcast	✅						Alpha	v1	1.0
JetStream KV	✅						Alpha	v1	1.7
Memcached	✅			✅			Alpha	v1	1.0
MongoDB	✅	✅	✅		✅	✅	Stable	v1	1.0
MySQL	✅	✅	✅		✅		Beta	v1	1.7
Oracle Database	✅	✅	✅	✅	✅		Alpha	v1	1.7
PostgreSQL	✅	✅	✅		✅	✅	Stable	v1	1.0
Redis	✅	✅	✅	✅	✅	✅	Stable	v1	1.0
RethinkDB	✅						Alpha	v1	1.0
Zookeeper	✅		✅				Alpha	v1	1.0

Amazon Web Services (AWS)

Component	CRUD	Transactional	ETag	TTL	Actors	Query	Status	Component version	Since runtime version
AWS DynamoDB	✅			✅			Alpha	v1	1.0

Google Cloud Platform (GCP)

Component	CRUD	Transactional	ETag	TTL	Actors	Query	Status	Component version	Since runtime version
GCP Firestore	✅						Alpha	v1	1.0

Microsoft Azure

Component	CRUD	Transactional	ETag	TTL	Actors	Query	Status	Component version	Since runtime version
Azure Blob Storage	✅		✅				Stable	v1	1.0
Azure CosmosDB	✅	✅	✅	✅	✅	✅	Stable	v1	1.0
Azure SQL Server	✅	✅	✅		✅		Stable	v1	1.5
Azure Table Storage	✅		✅				Beta	v1	1.7

Oracle Cloud

Component	CRUD	Transactional	ETag	TTL	Actors	Query	Status	Component version	Since runtime version
Autonomous Database (ATP and ADW)	✅	✅	✅	✅	✅		Alpha	v1	1.7
Object Storage	✅		✅	✅			Alpha	v1	1.6