🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Solace Dynamic routing
Is dynamic routing is same as dynamic destination binding
Dynamic routing as per rabbit all producer published to same queue, configured on routingKeyExpression for producer and consumer listener receives it based on bindingRoutingKey.
does this can be accomplished using stream bridge or BinderAwareChannelResolver??
Comments
-
Hi @akg17 ,
Solace PubSub+ is a publish subscribe broker. Dynamic routing is based on matching subscriptions to published topics and routing based on those matches. This is most closely comparable to Rabbit's Topic Exchange. Since you are a Rabbit user, I'd recommend you to read through my blog post that covers mapping Rabbit's exchange concepts onto a publish subscribe broker like Solace ( https://solace.com/blog/mapping-amqp-0-9-1-onto-pub-sub/ ).
So in a way your binding key in Solace would be your topic subscription and your application will receive messages for which their topic subscription matches any published topics.
You can find more details on our topics and how they work in our docs here: https://docs.solace.com/PubSub-Basics/Understanding-Topics.htm .0 -
Awesome, thanks for sharing @ChristianHoltfurth. I hadn't seen that blog before!
1
