State stores

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

NameCRUDTransactionalETagTTLActorsQueryStatusComponent versionSince
AerospikeAlphav11.0
Apache CassandraAlphav11.0
CouchbaseAlphav11.0
Hashicorp ConsulAlphav11.0
HazelcastAlphav11.0
MemcachedAlphav11.0
MongoDBStablev11.0
MySQLAlphav11.0
PostgreSQLAlphav11.0
RedisStablev11.0
RethinkDBAlphav11.0
ZookeeperAlphav11.0

Amazon Web Services (AWS)

NameCRUDTransactionalETagTTLActorsQueryStatusComponent versionSince
AWS DynamoDBAlphav11.0

Google Cloud Platform (GCP)

NameCRUDTransactionalETagTTLActorsQueryStatusComponent versionSince
GCP FirestoreAlphav11.0

Microsoft Azure

NameCRUDTransactionalETagTTLActorsQueryStatusComponent versionSince
Azure Blob StorageStablev11.0
Azure CosmosDBStablev11.0
Azure SQL ServerStablev11.5
Azure Table StorageAlphav11.0

Oracle Cloud Infrastructure (OCI)

NameCRUDTransactionalETagTTLActorsQueryStatusComponent versionSince
OCI Object StorageAlphav11.6

Last modified February 18, 2022: Update setup-jetstream.md (#2200) (428d8c2)