Preview features in Dapr are considered experimental when they are first released.
Runtime preview features require explicit opt-in in order to be used. The runtime opt-in is specified in a preview setting feature in Dapr’s application configuration. See How-To: Enable preview features for more information.
For CLI there is no explicit opt-in, just the version that this was first made available.
Current preview features
|Pluggable components||Allows creating self-hosted gRPC-based components written in any language that supports gRPC. The following component APIs are supported: State stores, Pub/sub, Bindings||N/A||Pluggable components concept||v1.9|
|Multi-App Run for Kubernetes||Configure multiple Dapr applications from a single configuration file and run from a single command on Kubernetes||
|Workflows||Author workflows as code to automate and orchestrate tasks within your application, like messaging, state management, and failure handling||N/A||Workflows concept||v1.10|
|Cryptography||Encrypt or decrypt data without having to manage secrets keys||N/A||Cryptography concept||v1.11|
|Service invocation for non-Dapr endpoints||Allow the invocation of non-Dapr endpoints by Dapr using the Service invocation API. Read “How-To: Invoke Non-Dapr Endpoints using HTTP” for more information.||N/A||Service invocation API||v1.11|
|Actor State TTL||Allow actors to save records to state stores with Time To Live (TTL) set to automatically clean up old data. In its current implementation, actor state with TTL may not be reflected correctly by clients, read Actor State Transactions for more information.||
||Actor State Transactions||v1.11|
|Transactional Outbox||Allows state operations for inserts and updates to be published to a configured pub/sub topic using a single transaction across the state store and the pub/sub||N/A||Transactional Outbox Feature||v1.12|
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.