Server vs WASM
The two interactive hosting models trade latency, scale, and offline support.
Interactive Server
- UI events run on the server over a SignalR connection
- Tiny download, instant start
- Needs a constant connection; latency per click
- Secrets and DB access stay on the server
WebAssembly
- Your .NET code runs in the browser
- Works offline once loaded
- Larger initial download
- Calls APIs over HTTP like a SPA