AspNetCore.Docs
AspNetCore.Docs copied to clipboard
dotnet
Signal R + Redis clustering Unclear Docs
The official docs says "Redis Clustering is a method for achieving high availability by using multiple Redis servers. Clustering isn't officially supported, but it might work." This isn't clear enough for almost every production level app. If you are using SignalR on a farm you need a backplane and are probably using Redis. That backplane needs to high availability otherwise it is simply not possible to provide an enterprise level solution. The docs have said this vague statement for years. We can't pretend that it's ok for this to be unknown when it comes up almost every single time someone tries to build an enterprise application using Signal R.
Currently everybody using SignalR has to go and do trial and error to see whether this vague statement means in practical terms it does work and then decide whether they can risk it being broken in the future since it's not officially suppported.
The optimum outcome for everyone would be it is officially supported and documented as such. It basically needs to be supported otherwise SignalR is not fit for enterprise without using a third party backplane provider.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: c548355c-d88f-b941-0622-56732973123b
- Version Independent ID: bddd7575-422d-4342-af48-f6b0979fb69a
- Content: Redis backplane for ASP.NET Core SignalR scale-out
- Content Source: aspnetcore/signalr/redis-backplane.md
- Product: aspnet-core
- Technology: aspnetcore-signalr
- GitHub Login: @bradygaster
- Microsoft Alias: bradyg
@bradygaster, should this more simply state at the moment Redis clustering isn't supported? Unless there is a specific situation where it is known to work and can be specified.
Appreciate the idea @wadepickett - i think the real solution here (and i mentioned this to @davidfowl) is that we put out what customers should expect from Redis and allow them to make their own decisions on if its performance is good enough for their scenario. I am not a fan of the "it might work" mention, as much as I would be an analysis of what Redis can do and what customers can expect from it, so they can make an educated decision.
