Blazor in more depth - Steve Sanderson & Ryan Nowak

In this talk, Blazor's two architects will take you deeper into the framework, showing a range of more advanced features and their internal workings. We'll dig into server-side Blazor and how we built the SignalR-based mechanism for efficiently streaming UI updates, as well as authorization in Blazor WebAssembly, and more.

Check out more of our talks, courses, and conferences in the following links:

[adefwebserver]

I love this presentation. Just the facts. They hide nothing, . All the source code is on GitHub. Most of their discussions about the code are on GitHub.

They acknowledge two 'issues of concern' with server side Blazor, latency and memory use.

Latency is simply not an issue if your users are on the same continent as you, and if they are not you can use something like Azure Front Door.

Memory use applies to *all* applications that store any "state" for their users in memory (I guess it would be possible to maintain state in a persistent file system, but then performance would suck).

[sarinnw]

NDC video recording should just the speaker little thumbnail on lower right corner. I like to see the content better on the small device.

[aceleful]

I am trying Blazor server but facing issue in load balancer, we are not enabling sticky sessions as per security reasons. So my load balanced web server app hosting in iis is not working.

[Robber]

What if you rum blazor server and dont want an external api? Passing round the token and checking it everywhere seems like a huge hassle. Normal asp just signInAsync and you are done..

[TrotterSoccer]

Late watcher...., but still.... Nice presentation!

[KieranDevvs]

People keep saying that threading isn't really necessary or important within Blazor but I would argue that completely. The whole idea behind Blazor / WebASM is to execute compiled target code in the browser to give a performance boost for things such as games and other intensive applications. Without threading, there's really no point in adopting a whole new paradigm like Blazor over the traditional options such as React or Vue, other than to unify your tech stack which IMO isn't a good enough reason.

[kdvtea]

It's a cool thing, and Steve works very diligently on it, but I can't see Blazor succeed in any way at all.


Why:


- 5000 concurrent connections sounds really bad, even on a small vm.
- Attack surface like DoS is HUGE with something like Server-Side-Blazor, WASM on the client doesn't help either as it's relatively new. I wouldn't get it approved.
- Personal opinion, but Razor is worse than attempting to parse HTML using Regex, EJS and anything else I've worked with. Also, every IDE I've worked with has some personal issues with parsing Razor as well, highlighting issues and so on.

- Competing technologies are way more mature and efficient. A lesser development effort cannot win against that.

[striker]

Lol, no, ain't gonna happen. Pretty late to the party there blazor.

[tbremard]

Why do not you use HttpContext.SignInAsync() to logon user into your frontend http session ?