Last post Jul 02, 2015 05:17 AM by Zhixing Lv - MSFT
Jun 26, 2015 12:05 PM|qingl77|LINK
Let's say you have one WebRole in Azure Cloud accepting Web request from multiple Web browsers using HTTP and forward to multiple on-premisses backend servers using SignalR. You have multiple instances of the WebRole in cloud to do load balancing.
On Web front, Web request from Web Browsers load balancing to WebRole instances. On backend, each backend server load balancing (using SignalR
Scaleout with Azure Service Bus) to connect to WebRole instances. Since SignalR is persistent connection, each connection will land to particular instance of WebRole and stick with this one-to-one connection until it ends.
The question is how to route a Web request designated to a particular backend server to the right WebRole instance connecting to the backend server at runtime.
There are ways to resolve the problem but they involve message queue in Cloud to decouple Web page HTTP connections with SignalR connections. Like
WebPage ---http---> WebRole_front --> Queue --> WebRole_back ---signalR---> backendServer.
Is there a better way to resolve this routing?
Jun 26, 2015 02:42 PM|qingl77|LINK
It seems SignalR groups can resolve this kind of problem easily. I will try.
Jul 02, 2015 05:17 AM|Zhixing Lv - MSFT|LINK
From a support perspective this is really beyond what we can do here in the forums.
If you cannot determine your answer here or on your own, consider opening a support case with us. Visit this link to see the various support options that are available to better meet your needs: