CODEWITHSUNDEEP
asp.net-mvcsignalrsignalr-hubsignalr.client
JohnB
JohnB

Reputation: 4359

Should we build our SignalR solution into a self hosted app or continue to use it directly within our MVC app?

We've currently got our SignalR 2.x Hub built directly into our MVC Web application. It basically works and now are thinking towards performance and scalability.

In terms of performance and scalability, is it better to have our SignalR hub be self hosted in it's own app than be buit into the MVC app directly?

What is the best strategy for building out a highly performant/scalable SignalR solution, especially as we scale out our application across a web farm?

Thanks, JohnB

Upvotes: 1

Views: 475

Answers (1)

Shachaf.Gortler
Shachaf.Gortler

Reputation: 5735

If you plane to scale signalR you will need to incorporate some sort of back-plane, this is needed if using a load balancer so if one client connects to one of the server all of the other server can send message to that particular client, The are server back plane support by SignalR sql,azure and redis If performance is an issue i will suggest Redis see here. and also here for more preformace orineted configurations.

That being said SignalR should be hosted in own app behind its own load balancer, that will give more control on it's scalability.

Upvotes: 1

Related Questions