Consider a "standalone" SignalR backplane solution

[davidfowl]

We can start with a basic implementation that is a standalone application that needs to be hosted in order to function, no fancy clustering just yet. Everyone connects to the SignalR backplane service and we treat it like a remote cache.

One downside of doing it this way is that the backplane service would need to be scaled out as well...

[grahamehorner]

I’m looking into something similar, with #ServiceFabric hub-spoke configurations and mesh, also looking at the possibility of a #ServiceFabric in memory #EF provider

[KPixel]

Is this similar to the idea I discussed here #684, replacing Redis with SignalR itself?

[davidfowl]

@KPixel basically, there are questions on how to scale out the signalr used for messaging though.

[analogrelay]

Retargetting this to focus on an on-premise "standalone" backplane, primarily for cases where Redis and Azure SignalR is infeasible (i.e. On-Premise Windows).