Spring Cloud Stream Solace - Sticky Load Balancing Implementation

Hi @msharpe ,
Correct, when trying to consume order the broker can really only give a stream of events to one consumer at a time and the broker relies on the user to define what that stream of events is. So if you are trying to essentially partition your larger stream into subsets in which order matters then you would usually do this by publishing to a well known topic hierarchy and do fine grained filtering in the topic subscriptions assigned to your queues.
@Aaron wrote a great blog on it here: https://solace.com/blog/consumer-groups-consumer-scaling-solace/ . Be sure to check out the “Using Solace Topics for Partitioning” section. If that doesn’t do what you need it to let us know as I’d love to hear more about the use case.
Hope that helps!