Reading — Blazor, Held Together

Blazor, Held TogetherComponent Discipline · Rule 3

Component Discipline

Rule 3Chapter I

Pick the hosting model per application, not per fashion.

Why this rule exists

Server gives you latency-sensitive simplicity, WASM gives you offline and scale-out for free, and Auto gives you both complexities at once. Each is right somewhere; none is right everywhere.

Blazor, Held Together

In practice

Interactive Server for internal, chatty, always-online tools. WASM for public apps that must scale or work offline. Choose per app and write the choice down.

Keep reading

5 of 12 · 36%