In my prior post, I have listed some of the APIs that you can use for developing applications where PubSub pattern fits well. In this one, I will give talk little bit more in detail about one of which is Service bus for Windows server and then share some practical guidance.
We are living an era of connected applications. And service bus for Windows server is one of the API/platform you can use to connect applications that may be dispersed and hosted on different platforms (Windows, Linux) in a one/way or bi-directional fashion. It is very like Windows Azure service bus, but differs as being hosted on your own data center.
Figure #1: The service bus for Windows server platform stack
Service bus services that runs on each ring node:
o Windows Fabric: Core clustering technology that manages a “ring” of nodes in the farm.
o Service Bus Message Broker: Manages the send and receive operations from Service Bus queues, topics and subscriptions.
o Service Bus Gateway: Serves as protocol head for supported Service Bus protocols. The gateway also performs security validation on incoming requests.
o Service Bus Resource Provider: Handles management requests from the Windows Azure Pack portal.
o Service Bus VSS Writer: Discovers and automates backup and restore operations using Microsoft Volume Shadow Copy Service (VSS) technology.
Here, in this post, I have shared some of my learning from past experience. Hope it helps. As side note, as an alternative, you can play with Windows Azure service bus then plan & deploy the same functionality on your own environment if you will.
As mentioned in Design considerations, can Relaying (P2P) be done in Service Bus For Windows? Are there some samples? Pointers to APIs?
You are correct DhanaKrishnasamy, it was not clear what I meant till now. Thanks for correction.
Nice article on recommendations for improved usage.
WSO2 Enterprise Service bus , an open source ESB solution which performs well in both linux and windows platforms, provides clustering to handle increased loads to ESB instances.
More detail can be located at .