https://v1-18.docs.dapr.io/operations/components/setup-pubsub/Recent content in Pub/Sub brokers on Dapr DocsHugoenhttps://v1-18.docs.dapr.io/operations/components/setup-pubsub/pubsub-namespaces/Mon, 01 Jan 0001 00:00:00 +0000https://v1-18.docs.dapr.io/operations/components/setup-pubsub/pubsub-namespaces/<p>In some scenarios, applications can be spread across namespaces and share a queue or topic via PubSub. In this case, the PubSub component must be provisioned on each namespace.</p> <div class="alert alert-primary" role="alert"> <h4 class="alert-heading">Note</h4> Namespaces are a Dapr concept used for scoping applications and components. This example uses Kubernetes namespaces, however the Dapr component namespace scoping can be used on any supported platform. Read <a href="https://v1-18.docs.dapr.io/operations/components/component-scopes/">How-To: Scope components to one or more applications</a> for more information on scoping components. </div> <p>This example uses the <a href="https://github.com/dapr/quickstarts/tree/master/tutorials/pub-sub">PubSub sample</a>. The Redis installation and the subscribers are in <code>namespace-a</code> while the publisher UI is in <code>namespace-b</code>. This solution will also work if Redis is installed on another namespace or if you use a managed cloud service like Azure ServiceBus, AWS SNS/SQS or GCP PubSub.</p>