Pub/sub brokers
The following table lists publish and subscribe brokers supported by the Dapr pub/sub building block. Learn how to set up different brokers for Dapr publish and subscribe.
Pub/sub component retries vs inbound resiliency
Each pub/sub component has its own built-in retry behaviors, unique to the message broker solution and unrelated to Dapr. Before explicity applying a
Dapr resiliency policy, make sure you understand the implicit retry policy of the pub/sub component you’re using. Instead of overriding these built-in retries, Dapr resiliency augments them, which can cause repetitive clustering of messages.
Table headers to note:
Header | Description | Example |
---|
Status | Component certification status | Alpha Beta Stable
|
Component version | The version of the component | v1 |
Since runtime version | The version of the Dapr runtime when the component status was set or updated | 1.11 |
Generic
Amazon Web Services (AWS)
Component | Status | Component version | Since runtime version |
---|
AWS SNS/SQS | Stable | v1 | 1.10 |
Google Cloud Platform (GCP)
Component | Status | Component version | Since runtime version |
---|
GCP Pub/Sub | Stable | v1 | 1.11 |
Microsoft Azure