Pub/sub brokers

    Dapr supports the configuration of multiple, named, pub/sub components per application. Each pub/sub component has a name and this name is used when publishing a message topic. Read the for details on how to publish and subscribe to topics.

    Pub/sub components are extensible. A list of support pub/sub components is here and the implementations can be found in the .

    The type of pub/sub is determined by the field, and properties such as connection strings and other metadata are put in the section. Even though metadata values can contain secrets in plain text, it is recommended you use a secret store using a .

    Topic creation

    Depending on the pub/sub message bus you are using and how it is configured, topics may be created automatically. Even if the message bus supports automatic topic creation, it is a common governance practice to disable it in production environments. You may still need to use a CLI, admin console, or request form to manually create the topics required by your application.

    HowTo: Configure Pub/Sub components with multiple namespaces

    Use Dapr Pub/Sub with multiple namespaces