4 ms·
Using Blazor (.net). It's been mostly a good experience. Fast UI updates, good programming model.
by mgamache 5y ago
Using Blazor (.net). It's been mostly a good experience. Fast UI updates, good programming model.
- mwattsun 5y agoI've been looking at it lately and the SignalR tech it uses. Very nice. My cursory Google research indicates a server using it can handle about 3000 users, which is not many, but for my purposes is fine. Blazor makes it completely optional, which I proved to myself by doing client side Blazor (dot net wasm) only and using an Apache server instead of IIS with ASP.NET. https://en.wikipedia.org/wiki/SignalR https://en.wikipedia.org/wiki/SignalR
- mgamache 5y agoRight, with .net core 6 the runtime wasm is much smaller. SignalR can be scaled if you need to, but for most sites 3000 concurrent users is plenty.
- wvenable 5y agoWe're migrating to server-side Blazor because of the good experience yet all of the things mentioned in this article are a concern for using this technology. A few things, especially around deployment and maintenance, are significantly less good when your clients are always connected. I'm currently trying to figure out mitigations.