State store component specs

The supported state stores that interface with Dapr

Table captions:

Status: Component certification status

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.

Name	CRUD	Transactional	ETag	Actors	Status	Component version	Since
Aerospike	✅	❌	✅	❌	Alpha	v1	1.0
Apache Cassandra	✅	❌	❌	❌	Alpha	v1	1.0
Cloudstate	✅	❌	✅	❌	Alpha	v1	1.0
Couchbase	✅	❌	✅	❌	Alpha	v1	1.0
Hashicorp Consul	✅	❌	❌	❌	Alpha	v1	1.0
Hazelcast	✅	❌	❌	❌	Alpha	v1	1.0
Memcached	✅	❌	❌	❌	Alpha	v1	1.0
MongoDB	✅	✅	✅	✅	GA	v1	1.0
MySQL	✅	✅	✅	✅	Alpha	v1	1.0
PostgreSQL	✅	✅	✅	✅	Alpha	v1	1.0
Redis	✅	✅	✅	✅	GA	v1	1.0
RethinkDB	✅	✅	✅	✅	Alpha	v1	1.0
Zookeeper	✅	❌	✅	❌	Alpha	v1	1.0

Name	CRUD	Transactional	ETag	Actors	Status	Component version	Since
AWS DynamoDB	✅	❌	❌	❌	Alpha	v1	1.0

Name	CRUD	Transactional	ETag	Actors	Status	Component version	Since
GCP Firestore	✅	❌	❌	❌	Alpha	v1	1.0

Name	CRUD	Transactional	ETag	Actors	Status	Component version	Since
Azure Blob Storage	✅	❌	✅	❌	GA	v1	1.0
Azure CosmosDB	✅	✅	✅	✅	GA	v1	1.0
Azure SQL Server	✅	✅	✅	✅	Alpha	v1	1.0
Azure Table Storage	✅	❌	✅	❌	Alpha	v1	1.0