Skip to content

Latest commit

 

History

History
28 lines (19 loc) · 1.53 KB

use-signalr-service.md

File metadata and controls

28 lines (19 loc) · 1.53 KB
Raw

Use Azure SignalR Service

Provision an Azure SignalR Service instance

Go to Azure Portal to provision a SignalR service instance.

For ASP.NET Core SignalR

See document

For ASP.NET SignalR

See document

Scale Out Application Server

With Azure SignalR Service, persistent connections are offloaded from application server so that you can focus on implementing your business logic in hub classes. But you still need to scale out application servers for better performance when handling massive client connections. Below are a few tips for scaling out application servers.

  • Multiple application servers can connect to the same Azure SignalR Service instance.
  • As long as the name of the hub class is the same, connections from different application servers are grouped in the same hub.
  • Each client connection will only be created in one of the application servers, and messages from that client will only be sent to that same application server. If you want to access client information globally (from all application servers), you have to use some centralized storage to save client information from all application servers.