Running Blazor in production, lessons learned
summary
Team runs Blazor in production for over two years, started seven days after GA and credits it with saving a project; they run Blazor Server, WebAssembly and Blazor Hybrid via .NET MAUI, use RavenDB for a call-for-papers site, and build a custom grid with responsive column removal and sign highlighting that works in production. They use AOT-compiled WebAssembly to cut startup time, prefer component-centric design, warn about Blazor Server memory/state (idle connections left for ~3 minutes) and solve loading with server prerender + preserved state.
AI-written summary · about
chapters (17)
- 0:00Intro
- 4:32Blazor - the Angular killer?
- 5:50Blazor, not another SPA framework
- 8:07Blazor has a naming problem
- 15:07Blazor Hybrid
- 19:03Web Components
- 19:57Is Blazor production ready?
- 21:37Unit Testing
- 23:04Razor or Code Behind?
- 26:03Building a component library
- 30:53Does companies use Blazor?
- 33:13Browser support
- 36:40Memory consumption
- 40:28Development speed
- 41:21Blazor Server is slow?
- 42:51Footprint / Loading time
- 49:31Questions?
related talks
51mHands-on Development Experience Using wasm Blazor
53mArchitecting Blazor Applications: An Angular inspired approach
16mFull stack web in .NET 8 with Blazor
49mArchitecting Blazor applications – An Angular inspired approach
49mArchitecture tips for hybrid apps with .NET MAUI and Blazor
42mState Management in Blazor Apps
59mBuild Blazor Components with Confidence and Precision
49mArchitecting Blazor applications – An Angular inspired approach