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.

Generic

NameCRUDTransactionalETagActorsStatusComponent versionSince
AerospikeAlphav11.0
Apache CassandraAlphav11.0
CloudstateAlphav11.0
CouchbaseAlphav11.0
Hashicorp ConsulAlphav11.0
HazelcastAlphav11.0
MemcachedAlphav11.0
MongoDBGAv11.0
MySQLAlphav11.0
PostgreSQLAlphav11.0
RedisGAv11.0
RethinkDBAlphav11.0
ZookeeperAlphav11.0

Amazon Web Services (AWS)

NameCRUDTransactionalETagActorsStatusComponent versionSince
AWS DynamoDBAlphav11.0

Google Cloud Platform (GCP)

NameCRUDTransactionalETagActorsStatusComponent versionSince
GCP FirestoreAlphav11.0

Microsoft Azure

NameCRUDTransactionalETagActorsStatusComponent versionSince
Azure Blob StorageGAv11.0
Azure CosmosDBGAv11.0
Azure SQL ServerAlphav11.0
Azure Table StorageAlphav11.0