Book Image

Web Development with Blazor

By : Jimmy Engström
Book Image

Web Development with Blazor

By: Jimmy Engström

Overview of this book

Blazor is an essential tool if you want to build interactive web apps without JS, but it comes with its own learning curve. Web Development with Blazor will help you overcome most common challenges developers face when getting started with Blazor and teach you the best coding practices. You’ll start by learning how to leverage the power of Blazor and explore the full capabilities of both Blazor Server and Blazor WebAssembly. Then you’ll move on to the practical part, which is centred around a sample project – a blog engine. This is where you’ll apply all your newfound knowledge about creating Blazor Server and Blazor WebAssembly projects, the inner working of Razor syntax, and validating forms, as well as creating your own components. You’ll learn all the key concepts involved in web development with Blazor, which you’ll also be able to put into practice straight away. By showing you how all the components work together practically, this book will help you avoid some of the common roadblocks that novice Blazor developers face and inspire you to start experimenting with Blazor on your other projects. When you reach the end of this Blazor book, you'll have gained the confidence you need to create and deploy production-ready Blazor applications.
Table of Contents (20 chapters)
1
Section 1:The Basics
4
Section 2:Building an Application with Blazor
14
Section 3:Debug, Test, and Deploy

Learnings from running Blazor in production

Ever since Blazor was in preview, we have been running Blazor Server in production. In most cases, everything has run without issues. Occasionally, we encounter a few problems and I will share those learnings with you in this section.

We will look at the following:

  • Solving memory problems
  • Solving concurrency problems
  • Solving errors
  • Old browsers

These are some of the things we ran into, and we have solved them all in a way that works for us.

Solving memory problems

Our latest upgrade did add a lot of users and with that, a bigger load on the server. The server manages memory quite well, but with this release, the backend system was a bit slow, so users ended up pressing F5 to reload the page. What happens then is that the circuit disconnects and a new circuit gets created. The old circuit waits for the user to perhaps connect to the server again for 3 minutes (by default).

The user now has a new circuit...