Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

4.9.2. Topic Exchange

A Topic Exchange routes messages based on the routing key (subject) of the message and the binding key of the subscription, just as a direct exchange does. The difference is that a topic exchange supports the use of wildcards in binding keys, allowing you to implement flexible routing schemas.
A Topic Exchange routes messages to queues where there is an match between the binding key of the queue and the routing key of the message. A binding key used to bind a queue to a Topic Exchange supports wild card matching, enabling developers to implement flexible routing schemes.
View larger image
A Topic Exchange routes messages to queues where there is an match between the binding key of the queue and the routing key of the message. A binding key used to bind a queue to a Topic Exchange supports wild card matching, enabling developers to implement flexible routing schemes.

Figure 4.3. Topic Exchange

Wildcard matching and Topic Exchanges

In the binding key, # matches any number of period-separated terms, and * matches a single term.

So a binding key of #.news will match messages with subjects such as usa.news and germany.europe.news, while a binding key of *.news will match messages with the subject usa.news, but not germany.europe.news.
Report a bug
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat