If you spend some time reading up on Udi Dahan's blog and material on SOA. He actually recommends breaking up your queues, ideally, by each message type. This allows you several benefits, although may somewhat complicate your deployment due to the number of windows services being deployed. After having a system up and using a service bus for some time now and not doing this, I can say there is merit to taking this approach. You can individually scale each piece of your business as needed, additionally one subscriber going down does not affect another unrelated services SLA. He even mentions starting and stopping virtual server(s) (that are nodes behind a load balancer) based on the elastic demand as you've described just by reading performance counters and determining a threshold.
This may be a drawn out answer to your question. To specifically answer your question about prioritizing a published message over others, no it doesn't. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
