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...