Menu
I'd like to make an informed choice towards a simple publish/subscribe architecture.
So I'm wondering: what does the Service Bus add that MSMQ can't do?
What are the drawbacks of the Service Bus?
Thx for enlightening me!
657
Service Bus is used to decouple applications and services from each other, providing the following benefits: Load-balancing work across competing workers. Safely routing and transferring data and control across service and application boundaries.
Blog:Service Bus for Windows Server: A Primer An Enterprise Service Bus (ESB) is a shared messaging layer that gives you a consistent, scalable and flexible means of coordinating across disparate, loosely-connected services to execute business processes.
Queues do not support Filtering.
Message Queuing (MSMQ) technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. Applications send messages to queues and read messages from queues.
The main functional difference is Service Bus provides out of the box support for message exchange semantics such as topic based routing via publish-subscribe.
MSMQ on the other hand is a lightweight store-and-forward queuing system, which supports point-to-point one way messaging.
Service Bus:
If you are looking at pub-sub frameworks then a popular one at the moment (free in single threaded mode) is NServiceBus, which sits on top of MSMQ, though has swap-able transport.
146
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
