nservicebus-distributor

What is the best way to route NServiceBus messages to specific clients?

阅读更多关于 What is the best way to route NServiceBus messages to specific clients?

问题 Let's say I have a ClientRequestMessage message that contains a request for a specific Client . A web application will generate these requests and they need to be sent to the correct Client for handling. I can think of a few options for this. I could have a single queue that all messages go to and specific client handlers check a property (like ClientId ) to decide whether they care about it. This feels wrong on many levels to me though. I could publish a message to all of the clients and

NServiceBus: Pros and Cons of using NServiceBus Distributor

阅读更多关于 NServiceBus: Pros and Cons of using NServiceBus Distributor

问题 I am considering using a Network Load Balancer to load balance messages between my subscriber instances, instead of using the NServiceBus distributor (which is basically just a software load-balancer from what I can tell). Each subscriber instance will have a queue of the same name for messages to be delivered to, and there will be a virtual IP that round-robins between the subscribers. The publisher will only know about the virtual IP and queue name. Here is what I understand as the pros and

What is the correct way to use the timeout manager with the distributor in NServiceBus 3+?

阅读更多关于 What is the correct way to use the timeout manager with the distributor in NServiceBus 3+?

问题 Version pre-3 the recommendation was to run a timeout manager as a standalone process on your cluster, beside the distributor. (As detailed here: http://support.nservicebus.com/customer/portal/articles/965131-deploying-nservicebus-in-a-windows-failover-cluster). After the inclusion of the timeout manager as a satellite assembly, what is the correct way to use it when scaling out with the distributor? Should each worker of Service A run with timeout manager enabled or should only the

NServiceBus: Pros and Cons of using NServiceBus Distributor

阅读更多关于 NServiceBus: Pros and Cons of using NServiceBus Distributor

I am considering using a Network Load Balancer to load balance messages between my subscriber instances, instead of using the NServiceBus distributor (which is basically just a software load-balancer from what I can tell). Each subscriber instance will have a queue of the same name for messages to be delivered to, and there will be a virtual IP that round-robins between the subscribers. The publisher will only know about the virtual IP and queue name. Here is what I understand as the pros and cons of doing this: PROS No need to install NServiceBus Distributor One less thing that would need to