Hi All,
First off all, these questions all pertain to the Windows Service Bus (on-premise), cloud services are unfortunately not available to use because of the massive investment the company has already made in infrastructure (and the big boss said so :)
We've implemented WSB in our lab environment using 3 nodes and for messaging it works a treat. We're happy with the performance and resiliency the product has to offer.
However, we need direction in the following scenarios :
1.Multiple Sites
We have several sites globally that we would like to communicate between. However, the limitation for MSB are 5 nodes I believe. Additionally, the connectivity between some of these sites are horrific. Should we configure 3 nodes at each site and if so, how
do we facilitate communication?
2.Not just message goodness
One of our developers are referring to a "hub/spoke" pattern for our existing WCF & WebAPI services. Essentially he wants to make the hub the central of all communication internally and between sites. Kind of like WCF relay's. Additionally, some
of our sites have their own services.
I'm slightly skeptical of this idea as I believe there is an inherent latency in this. For example, If we'd like to call GetAvailableParts() in our site, one service is called but GetAvailablePArts() from another site could have a completely different contract.
A different example could be that all services are aware of the bus but not each other. The bus would facilitate communication.
How would we go around doing this or should we even consider it?
Any help would be appreciated!