Blazor WebAssembly
Server-side Blazor
The workload is distributed to each user.
The server is responsible for resources. Like, SignalR instances.
Browser dependency.
No Browser dependency.
Limited Access to .Net Assembly. As it’s work with a mono implementation that supports the majority of .NET Standard 2.0 APIs.
Full Support at runtime of .Net Assembly. As it’s work on .Net Core Server.
On the first request, All the DLLs will be loaded and executed in the browser only.
All the DLLs will remain on the server only and executed and secure on the server. Only UI will be updated, and the updates are exchanged with the client, using SignalR.
Full support for Offline with progressive web applications (PWA).
No support for offline mode. It’s Requires an active network connection for the client interactions.
Full support for a content delivery network (CDN). So, can be hosted as a static website and served from CDN.
Requires an active server that supports ASP. NET to function.
Require low latency networks. Because most of the functions are executed on the client only.
Relies heavily on server-side communication for rendering.
Thick client. Due to more assemblies at the browser, the first request download size is big.
Thin client. No assemblies required to be downloaded at the browser, so page size is very less.
