Menu
We are using SignalR in our application, and we having some issues with it, such as calls failing and not consistently connecting. So I want to know if there is a good alternative to SignalR that we can use with .NET. For example, would socket.io be a good option?
866
For most applications, we recommend SignalR over raw WebSockets. SignalR provides transport fallback for environments where WebSockets isn't available. It also provides a basic remote procedure call app model. And in most scenarios, SignalR has no significant performance disadvantage compared to using raw WebSockets.
WebSockets is actually the underlying transport that SignalR uses, at least most of the time. SignalR has the ability to fall back to other ways of transporting messages, such as long-polling over HTTP. This is useful in situations where you don't have WebSockets support.
ASP.NET Core SignalR is an open-source library that simplifies adding real-time web functionality to apps. Real-time web functionality enables server-side code to push content to clients instantly. Good candidates for SignalR: Apps that require high frequency updates from the server.
All the concepts explained in the last article will be shown implemented in some of the most modern technologies currently available for building a powerful and secure WebRTC solution – Microsoft SignalR (with . NET Core 3.1) as our socketing and backend choice, and Angular 11 as our frontend client choice.
I'm not sure about how you want to use Node.js with ".Net"? Node.js is a JavaScript interpreter. If you want to write your backend with Nodejs, you could have a look at socket.io.
If you want to stick with ".Net" you could use Websockets directly, but this would be a little more low level since SignalR bases on WebSockets.
112
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
