with ASP.NET Core (based on this) allows to scale-out the number of connections Build serveless real-time apps using Azure Functions (v2) bindings it is possible to "react" to a whole series of events (storage, queue, http trigger...) Send messages from server to client with the REST API integrate with other apps that they can call the API and "push" informations to the clients tips...
choose the best transport among WebSocket, Server-Sent Events e Long Polling Hubs an hub is a high level pipeline which allows clients and servers to call each other, passing "strongly-typed" parameters to the methods. The message contains the name of the method to be invoked and the related parameters. Therefore exists a real "contract" between client and server
ASP.NET Core SignalR Server Hub Web App Console App Azure SignalR Service Server Endpoint Client Endpoint Xamarin Web App Console App What you want REST API
SignalR Service and SignalR Server (5 by default), used for two-way communications with clients Client connections Clients are connected directly to SignalR Service, url and access token are resolved by the endpoint "negotiate" Data transmit 1 to 1 mapping between client connection and relative server connection that takes charge of it. Therefore SignalR Service acts as a transport layer between server and clients, completely managing the connections (scalability)