Blazor in more depth
summary
Explains how Blazor Server compiles Razor to C# that emits render frames, diffs those frames to produce minimal DOM edits, and ships updates over SignalR using MessagePack, typically ~200–500 bytes per interaction. Describes server state kept in memory with a secret reconnect ID and encrypted markers, shows a headless-client test that hits 5,000 concurrent clients on a small VM (20,000 on a bigger one) and demos custom auth by storing a token in localStorage and sending it as a Bearer header.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:25At a high level
- 3:29Blazor Server
- 5:19Primitives of components
- 6:15Writing Blazor Code
- 7:52What does the compiler output
- 55:21Some ideas for ORA
related talks
36mBlazor - Full Stack Web Development in C# Only
35mScaling Blazor Server Apps with Azure
01h 02mBlazor in more depth
58mWelcome to Blazor
01h 03mBlazor, a new framework for browser-based .NET apps
46m.NET: What's Blazor - Front .NET
47mBlazor - Next Generation UI with .NET 6
51mComponent-based C# and Razor Programming in Blazor
