Blazor Server opens a SignalR connection to each client, does all the heavy lifting and pushes the resulting HTML to the client. This is not very scalable and you will need powerful servers if you get many users. WebAssembly is the entire application downloaded to the client, and the client does the heavy lifting. Then you just make HTTP calls to an API to get/post data. WASM require more coding, but scales better and runs better
How does blazor server do the downloading tho? If I am on my phone and using mobile data, I don't want to download 10mb every time I go to your page. I want the thing to be downloaded or cashed permanently. Now how does one achieve this? A client side app is only any good if you are not pumping out 9mb requests every time your user goes to your website from scratch. I say they only go there ones, and even if they leave and come back later, they will still use the downloaded code. Client side should only check the server for potential code updates on load. Does blazor server do this?
the download is cached, so its a single download. look at any of the big SPAs out there written in react and look at how much JS alone they are downloading...
Thank you for the comparison walkthrough!
Great video. Very helpful.
Very clear, nice and under-rated video. Thank you
Great video!! I am your subscriber no. 359
Nice to meet you!
Thanks, looking forward to the next one 🙂
More to come!
Blazor Server opens a SignalR connection to each client, does all the heavy lifting and pushes the resulting HTML to the client. This is not very scalable and you will need powerful servers if you get many users. WebAssembly is the entire application downloaded to the client, and the client does the heavy lifting. Then you just make HTTP calls to an API to get/post data. WASM require more coding, but scales better and runs better
How does blazor server do the downloading tho? If I am on my phone and using mobile data, I don't want to download 10mb every time I go to your page. I want the thing to be downloaded or cashed permanently. Now how does one achieve this?
A client side app is only any good if you are not pumping out 9mb requests every time your user goes to your website from scratch. I say they only go there ones, and even if they leave and come back later, they will still use the downloaded code. Client side should only check the server for potential code updates on load. Does blazor server do this?
It does the download only once.
the download is cached, so its a single download. look at any of the big SPAs out there written in react and look at how much JS alone they are downloading...