Pub/Sub brokers

    Dapr integrates with pub/sub message buses to provide applications with the ability to create event-driven, loosely coupled architectures where producers send events to consumers via topics.

    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.

    A pub/sub is described using a file:

    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

    Visit this guide for instructions on configuring and using pub/sub components.

    Use Dapr Pub/Sub with multiple namespaces