@TomF I can not really relate your reply to what i needed clarification on and see some problem.
When message ordering is related to exclusive queues then i wonder how you scale to have multiple parallel consumers to handle workload on subscriber/consumer side ?
So key question is how does Solace support ordering with high volumes ?
So please tell me how you scale this example:
Events 1 mio per hour Distinct Object: 100000 Order is needed Processing of message takes 50 ms
Messages/sec = 20
Throughput: 3600 seconds * 20 = 72000 msg/hour
So you need to scale with concurrent consumer to handle this volumes in parallel.
So 10 parallel consumers (to have some buffer for peaks) would solve the problem but that is not possible with exclusive queues. Right ?
The only options i can see to solve that problem are:
Switch to Push Subscription RDP - that decouples the publish from processing (the slow part is the processing on consumer) - You can scale up to 50 calls to endpoint in parallel. Sure you can add some partition field in topic and filter on that. But that is not an out of the box solution which is nicely solvable by providing a feature of partitions to split up the big work into smaller chunks. Order Id you can not add just as filter as you get orders randomly. So partition could be on region order belongs to or even or uneven order or MODULO to get any split you want. MOD(orderId, 10) provides a split of 10 parallel partitions.