nservicebus

Is it possible to configure an endpoint to act as a worker retrieving jobs from a distributor AND subscribe to some kind of messages? I have the following scenario ( adapted to sale terminology) *) a central department publishes every now and then a list of the new prices. All workers have to be notified. That means, a worker should subscribe to this event. *) when a new order arrives at the central, it sends it to the distributor, which send it to the next idle worker to be processed. That means, a worker have to be configured to receive messages from the distributor. I use the following

I am trying to understand if/how this works. Can SignalR and NServiceBus be used together to support full duplex on a web farm where the request could be sent from a server then later the response would come back but the user may be on another server. The use case for this would be a user submits a form which then takes a while to process say 3-5 minutes. During that time the user is doing other things and could be switching between servers due to load balancing. Once the process is complete it would send a response back which would show a notification to the user. If there are some articles

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

As a exercise I'm trying to find an example which implements competing consumer. many producers - > MSMQueue <- competing consumers So far I did not find any documentation on how to achieve this. My first attempt to figure out how is implemented in MassTransit or NServiceBus failed to many layers of indirection. Any help will be greatly appreciated. Cocowalla With MassTransit and MSMQ you can achieve this using the Distributor component. Note that if you use MassTransit with RabbitMQ instead of MSMQ, you can implement a competing consumer scenario without using the Distributor, simply by

I am curious if it even makes consider BizTalk for the implementation of a pub/sub messaging architecture (basically what you can do with NServiceBus or MassTransit is all I really need). My manager tends to want to stick with frameworks provided directly from Microsoft and so as part of my due diligence as to which one to use I need to give a good set of pro/cons for both sides. Any guidance would be greatly appreciated! One of the major cons of a Broker is that it is very difficult to version and upgrade. You would have to stop the flow of messages to upgrade a particular endpoint(s). A

Anyone using NServiceBus 2.0 successfully with Unity 2.0? I've tried to compile sources of NServiceBus.ObjectBuilder.Unity.dll against Unity 2.0 assemblies but got several compile-time errors because of changed/deleted signatures of many object methods in new Unity. In the documentation Udi Dahan says that attaching any container is as easy as implementing 5 methods of IContainer . But when i look into NServiceBus.ObjectBuilder.Unity implementation i see that there is a LOT more work to be done. Why it is so? Unity, by default, behaves different from what NSB expects. That's why there is a

I'm looking to gain a better understanding of why it is recommended to never Publish() messages from a website using NServiceBus ( NServiceBus Documentation , scroll about two thirds of the way down). Doesn't it make semantic sense to Publish() events, and to Send() commands? If so, I think it makes sense that a web application can both Publish() and Send() :-) Also, given that using Publish() doesn't require the web application to know about the recipients of the messages (Send() requires the web application to have all recipient endpoints configured), it feels like Publish() is a better