So finally blazor webassebmly is lunched by microsoft on 19th May 2020. This is a fully-featured and supported release of Blazor WebAssembly that is ready for production use. Full stack web development with .NET is now here! So this video is all about Client Side Blazor vs Server Side Blazor. I also talk about the pros and cons of both and end this blog post with conclusion.
On a side note, I also make a video about this topic on YouTube click here to watch the video. (if you understand Urdu or Hindi).
Web Assembly Came into Picture
How Client Side Blazor Work
How Server Side Blazor Work
Shared Benefits of Client Side Blazor and Server Side Blazor
- Full Stack With Dot NET
- Code Sharing Between Back End and Front End
Pros of Client Side Blazor
- Low server overhead
Cons of Client Side Blazor
- More Payload on Client Browser
- Disconnected Approach
Pros of Server Side Blazor
- Less Payload on Client
- Less Abstraction on Server
- Pre Rendering
Cons of Server Side Blazor
- Connection is Required
- More Resources Required on Server
so if we take a look at both technologies client side blazor vs server side blazor. We can see that both have there own advantages and disadvantages. In some scenarios client work better and some cases server work better. This is totally depend on your personal choice which one to choice. One thing that I can mention here is all these new technologies like webassebmly and blazor open new doors for other programming languages to come over web. As we have different choices our back end and choice what suites us in future we have also multiple options on client side to choose best fit for our business need.