SignalR with Service Fabric Unlimited Web API

Got some info from this related question: Using SignalR with Azure Service Fabric

Quote from a quote from this comment history: "After deploying this application, you can see that some signalR calls fail, and some succeed ..."

I just want to know if someone had a similar implementation (signalR with Web API ...). And I don't want to set the instance counter 1 for the stateless API.

+2
source share
1 answer

You can configure the LoadBalancer, which the Fabric service uses to save the session. This will cause a particular client to always be in the same node.

You can do this by contacting the LoadBalancer assigned to the service cluster on the azure portal. Then go to the "Load Balancing Rules", select the rule that is responsible for the signalR port, and set "Session persistence" to "Client IP". This can also be done from a PowerShell or ARM template.

+9
source

Source: https://habr.com/ru/post/1627736/


All Articles