NServiceBus vs Windows ServiceBus

Question

Can anyone shed light on the differences between the new release of Windows ServiceBus (by assumption, not with Azure) and NServiceBus?

Looking for a detailed answer to the question that Windows SB may be missing, as I know what NSErviceBus can do:

• Is it a real service bus, not just a message broker that uses queues?
• Can it support message polymorphism? (Message subclasses are other messages and handlers that support this hierarchy.
• Long-running processes and correlation
• To scale

Answer 1

I am responsible for supporting Windows Azure ServiceBus on NServicebus. And, in my opinion, this new Windows Server Servicebus provides the same features as Azure ServiceBus. Therefore, in my opinion, this will be a good match with NServiceBus instead of a competitor (like Windows Azure ServiceBus) and can be used instead of msmq.

To answer your questions

• The new service server is a broker that uses queues
• Messages on the service bus are, after all, whole lines; the service service itself does not have additional support for message types, hierarchies, handlers, etc. Typically, WCF or NServiceBus is used for this.
• Support for lengthy processes and correlation is missing. It has some overlapping features with NServiceBus, although since it can do subscriptions / topics, it can also postpone messages as well as filters.
• It is designed to scale.

Hope this helps?

Regards, Yves