Setting SignalR Hubs

Overview

Normally, when our application is scaled out, we'll be running multiple instances of the same application that was created from the same code. Different systems allow us to scale applications—Docker Swarm, Kubernetes, Azure Service Fabric, etc.

The entry point into the application for the clients would typically be a reverse proxy, a load balancer, or a combination of both. Basically, some gateway software would accept the initial request. And then this request would be rerouted to a specific instance of the application. Typically, there would be some algorithm in place to ensure that it’s an instance with a reasonably low load that the request gets routed to.

There are many different ways we can scale our application. However, the scope of this chapter is to show us the general principles of working with SignalR backplane rather than showing a specific way of scaling out our web application. This is why we won’t cover any specific scaling-out techniques. Instead, we'll just manually create two copies of a web application and connect them to the same instance of the Redis backplane. Then, we'll just connect different ...