Hello team,
I’ve just realized that deliver-to-one together with Subscriber priority is deprecated now. That was an extremely useful combination because we were able to make our high frequency subscribers highly available - active primary instances with higher subscriber priority receiving messages in primary datacenter and stand-by instances with lower priority in another datacenter not receiving any messages but just being ready in case of a disaster.
Deliver to one (with round-robin) is available with Shared subscriptions but that is not enough. Is there a way how to achieve functionality provided by Subscriber priority in a strategic way please?
I would really appreciate any help.
Thank you in advance!
Peter
Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:
Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.
AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a 
. If my response doesn’t make sense for your topic, please react to it with a 
.
I don’t have the information on that, but you might find what you’re looking for in the following sources:
Hi Peter,
This is an issue with documentation and how we discourage use of some of the features in the APIs.
We have, rightly or wrongly, marked pretty much all of DTO, subscriber local, and, subscriber network priority as deprecated within the API. This is because, for load balancing, shared subscriptions is a better alternative. However, shared subscriptions do not support the concept of priority and therefore do to support the type of failure / resilience routing you require.
For fail-over use-cases, the use of DTO priority is still the only option for Direct message consumers. While the APIs show this as deprecated the feature is not going away in the short / medium term. You can continue to use DTO and Priority until such time as we support priority within shared subscriptions. As an aside Solace uses DTO for Solace PubSub+ cache snap requests, so removal of this feature would affect our cache product.
If you require any further clarification please connect with me directly.
Thanks,
Mat
Understood! Thank you, Mat!
Are you aware of plans/horizon for implementation of priority subscribers please for Shared subs? (asking here as it might be beneficial for the community)
I am actually a big fan of this new concept of Shared subscriptions because DTO is dangerous indeed (someone “unacquainted” connecting to the topic just for browsing but in reality consuming messages from the business flow) which is highly likely the reason for this new strategy, right?
Thank you,
Peter
Hi Peter,
Currently there is no roadmap item to support priority within shared subscriptions. To date this has been on the wish list competing with other features for resources and delivery.
As you correctly state shared subscriptions are ‘DTO done correctly’. It decouples producer and consumer where DTO couples them. You can have multiple shares for the same topic where as in DTO you can only have 1. This list goes on.
I have a few clients now asking about DTO deprecation and lack of support for priority in shared subscription. This might be enough to raise the priority enough to get a date for delivery.
/Mat
1 Like