SignalR sucks
-
That looked good to me too, and also NATS (especially with future Docker microservices development in mind), but one of my colleagues already beat me to it with a Proof of Concept using ZeroMQ before I could even start a discussion about it, guess I'm getting too old and slow :sigh: And I must say, the more I read about ZeroMQ the more enthousiastic I get, it's even developed by a Dutch guy !
Never heard of NATS (just read your experience on that list). My biggest objection to ZeroMQ would be the following:
Some guy named Tim wrote:
More complicated scenarios require more setup ZeroMQ is very fast due to its simplicity, but as a result of this, doing anything harder than passing messages between 2 peers will require a lot more work from the user.
SignalR is (usually) a one-to-many broadcast, with support for channels. That sounds more like topics than queues, and according to this Tim topics aren't supported in ZeroMQ. RabbitMQ (and ServiceBus) do support topics out of the box. Although reading the ZeroMQ website it also seems they support topics as well, so Tim might just be a dirty little liar :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
I thought RabbitMQ was a message que system. Does RabbitMQ implement WebSocket type of technology?
I didn't think so, but then I found RabbitMQ Web STOMP Plugin — RabbitMQ[^]. I'm not sure how Rick wants to implement queueing in a browser, but with over 350,000 packages in the npm repository I'm sure there's one for connecting your queue to JavaScript :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
Me and my colleagues at work have totally had it with SignalR and it's erratic behaviour, everything seems to work fine locally, but as soon as it's tested in a production environment unexplainable problems occur. Also there does not seem to be anything to find about these problems on the internet, like long delays on message delivery :mad: Are we the only ones having these problems ? We are thinking about switching to ZeroMQ, see: message-queue-servers[^]
Just a wild stab in the dark, but is Symantec Endpoint Protection involved in the equation?
I wanna be a eunuchs developer! Pass me a bread knife!
-
Me and my colleagues at work have totally had it with SignalR and it's erratic behaviour, everything seems to work fine locally, but as soon as it's tested in a production environment unexplainable problems occur. Also there does not seem to be anything to find about these problems on the internet, like long delays on message delivery :mad: Are we the only ones having these problems ? We are thinking about switching to ZeroMQ, see: message-queue-servers[^]
-
Me and my colleagues at work have totally had it with SignalR and it's erratic behaviour, everything seems to work fine locally, but as soon as it's tested in a production environment unexplainable problems occur. Also there does not seem to be anything to find about these problems on the internet, like long delays on message delivery :mad: Are we the only ones having these problems ? We are thinking about switching to ZeroMQ, see: message-queue-servers[^]
Having a right skill is knowledge. If you don't know, then don't blame/insult the tool. Rather try to acquire the knowledge.
-
Having a right skill is knowledge. If you don't know, then don't blame/insult the tool. Rather try to acquire the knowledge.
But not all tools are created equal.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Me and my colleagues at work have totally had it with SignalR and it's erratic behaviour, everything seems to work fine locally, but as soon as it's tested in a production environment unexplainable problems occur. Also there does not seem to be anything to find about these problems on the internet, like long delays on message delivery :mad: Are we the only ones having these problems ? We are thinking about switching to ZeroMQ, see: message-queue-servers[^]
-
Just a wild stab in the dark, but is Symantec Endpoint Protection involved in the equation?
I wanna be a eunuchs developer! Pass me a bread knife!
Good one, we'll check that !
-
What version of SignalR are you using, i.e. .net framework or .net core? BTW, they never tell you that if SignalR is on a port, in production, it's likely the firewall will block you at most companies.
I know they are using self hosted .NET Core SignalR and maybe .NET too ... Microsoft.AspNet.SignalR.Core.dll 2.2.6
-
did u enable trace log..
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
-
Pretty much anything of that sort is created by architecture astronauts and will not fullfil any particular need.
PIEBALDconsult wrote:
architecture astronauts
This is priceless. Will be reused.
-
Me and my colleagues at work have totally had it with SignalR and it's erratic behaviour, everything seems to work fine locally, but as soon as it's tested in a production environment unexplainable problems occur. Also there does not seem to be anything to find about these problems on the internet, like long delays on message delivery :mad: Are we the only ones having these problems ? We are thinking about switching to ZeroMQ, see: message-queue-servers[^]
Are you using the .NET Full Framework or the .NET core? I only started with .NET core 2.1 and built distributed batch processing work queue and it's working fine and even has good performance, tested crossplatform and scaled on aws cloud without problems. I did experiment with large messages (10MB) but (de)serialization performance caused me to stick to small packets and strip of unnecessary data.
-
Are you using the .NET Full Framework or the .NET core? I only started with .NET core 2.1 and built distributed batch processing work queue and it's working fine and even has good performance, tested crossplatform and scaled on aws cloud without problems. I did experiment with large messages (10MB) but (de)serialization performance caused me to stick to small packets and strip of unnecessary data.
The problems are mainly with .NET Core SignalR. Large messages is not what SignalR is meant for, and we only use small messages.
-
Me and my colleagues at work have totally had it with SignalR and it's erratic behaviour, everything seems to work fine locally, but as soon as it's tested in a production environment unexplainable problems occur. Also there does not seem to be anything to find about these problems on the internet, like long delays on message delivery :mad: Are we the only ones having these problems ? We are thinking about switching to ZeroMQ, see: message-queue-servers[^]
have you looked at ServiceStack Server Events. as an alternative to SignalR?
Over..
-
Me and my colleagues at work have totally had it with SignalR and it's erratic behaviour, everything seems to work fine locally, but as soon as it's tested in a production environment unexplainable problems occur. Also there does not seem to be anything to find about these problems on the internet, like long delays on message delivery :mad: Are we the only ones having these problems ? We are thinking about switching to ZeroMQ, see: message-queue-servers[^]
As Sander Rossel and Scott Serl pointed out, SignalR's goal is not to be a message queue service. The fact that you can use it as one does not mean you should.
Paulo Gomes Measuring programming progress by lines of code is like measuring aircraft building progress by weight. —Bill Gates Everything should be made as simple as possible, but not simpler. —Albert Einstein
-
Yes, but we did not get any wiser, that is the most frustrating thing about SignalR: you don't have a clue what is going on :sigh:
these kind of things may need some investigation and thought..also configuration management..like what is the difference between the development and production environments ? is there a firewall..are the ports enabled... is there dpi ssl filtering ...packet inspection.... is there some timeouts that are causing connections to drop...latency...is there firewall or av on the production.. any lockdowns... are the pipes open properly...https://forums.asp.net/t/2096572.aspx?why+signalr+so+slow.... https://docs.microsoft.com/en-us/aspnet/signalr/overview/testing-and-debugging/enabling-signalr-tracing
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
-
have you looked at ServiceStack Server Events. as an alternative to SignalR?
Over..
Thanks for the tip, I will have a look at it !
-
PIEBALDconsult wrote:
architecture astronauts
This is priceless. Will be reused.
Apparently Joel Spolsky coined it. Look it up.
-
Apparently Joel Spolsky coined it. Look it up.
-
Me and my colleagues at work have totally had it with SignalR and it's erratic behaviour, everything seems to work fine locally, but as soon as it's tested in a production environment unexplainable problems occur. Also there does not seem to be anything to find about these problems on the internet, like long delays on message delivery :mad: Are we the only ones having these problems ? We are thinking about switching to ZeroMQ, see: message-queue-servers[^]
I have found that disabling all the fallbacks and forcing SignalR to use websockets makes a huge difference. Also if you are using nginx there is a config setting that limits the number of connections to 300 that you need to bump up. Also I am not sure in what capacity you are using SignalR, but you might want to check out the below library (disclaimer: I'm the author) Entity Signal - Real Time Entity Framework (EF) and ASP.NET core[^]
