3 ms·
>Given the author mentions C# is part of their stack I don't know why they didn't mention signalr or use that instead of rolling their own solution. Not saying
by whoknowsidont 2y ago
>Given the author mentions C# is part of their stack I don't know why they didn't mention signalr or use that instead of rolling their own solution.
Not saying this is why but SignalR is notoriously buggy. I've never seen a real production instance that didn't have issues. I say that as someone who probably did one of the first real world, large scale roll outs of SignalR about a decade ago.
- rswskg 2y agoI believe it's changed alot since then? I was abit cynical of it from that initial experience but recent usage of it made it seem reliable and scalable.
- davidgl 2y agoWe use it in a production system on the aspnetcore stack, and it's been bulletproof for a number of years. We have lots of proxies in the way, and old tech on certain networks, and at this moment we are 97% websockets, 2% server side events, 1% long polling, and it's all transparent to me, brilliant.