Would someone be able to shed some light on the differences between the newly release Windows ServiceBus (on premise, not Azure) and NServiceBus?
Looking for a detailed answer what the windows SB may be missing as I'm familiar what NSErviceBus can do:
- Is it a real service bus and not just a message broker that uses queues?
- Can it support message polymorphism? (Messages subclassing other messages and handlers supporting this hierarchy
- Long running processes and correlation
- Scale out
I'm responsible for the Windows Azure ServiceBus support in NServicebus. And in my opinion this new Windows Server Servicebus provides the exact same capabilities as the Azure ServiceBus. So in my opinion it will be a good match with NServiceBus instead of a competitor (just as the Windows Azure ServiceBus is) and could be used instead of msmq.
To answer your questions
- The new servicebus is a broker that uses queues
- Messages on the servicebus are just strings in the end, the servicebus itself has no additional support for message types, hierarchies, handlers etc. Typically you would use WCF or NServiceBus for this.
- There is no support for long running processes nor correlation. It does have some feature overlap with NServiceBus though as it can do subcriptions/topics, it can also do deferral of messages as well as filters.
- It's designed to scale out.
Hope this helps?
Kind regards, Yves
来源：https://stackoverflow.com/questions/11526982/nservicebus-vs-windows-servicebus