Improve SignalR Redis Cluster section

[VilleKylmamaa]

SignalR Redis backplane documentation informs about the trade-off that increasing the number of nodes in a Redis Cluster decreases the message throughput of the backplane (source video, and source slides).

Also mention that in the SignalR app, all the Redis nodes should be included in the Redis connection string or added as EndPoints in the ConfigurationOptions object.

Reference issue: dotnet/aspnetcore#46408

[guardrex]

Thanks @VilleKylmamaa ... I'll perform an edit pass after technical review. Done!

[VilleKylmamaa]

I removed the Redis Sentinel suggestion because of uncertainty whether it is supported out of the box. You can trigger Sentinel mode in StackExchange.Redis by adding a service name to the connection string (https://stackexchange.github.io/StackExchange.Redis/Configuration), but I am unsure if it works with SignalR. I failed to make it work properly in quick testing. It should be confirmed to work if it is to be added in the documentation.

[guardrex]

@VilleKylmamaa ... See if my updates broke any of the meaning.

[VilleKylmamaa]

@guardrex The edits are good 👍

[guardrex]

Thanks @VilleKylmamaa ... We'll stand-by for a bit until @BrennanConroy is free to take a look.

[guardrex]

Let's see how this looks ...

There's a tradeoff between the number of nodes in the cluster and the throughput of the backplane. Increasing the number of nodes increases the availability of the cluster but decreases the throughput because messages must be transmitted to all of the nodes in the cluster.

[guardrex]

🎉

We made it! Thanks @VilleKylmamaa! 🚀

Thanks, @BrennanConroy! 🎸