Blazor server side. Client side with DB connections

Question

Hello,

I am working on a Blazor server side application.
Now do I use multiple databases on different part of the website.
How is it possible that client A that is on a page that use Database Z stays connected while client B on Database Y is also connected?
Both pages are being build fine and both has a call to the database every second.
So when client A is on the page it is getting updated with the new data from the databse every second. But when client B goes to another page that uses Database Y. Connection to database Z is stopped and client A does not get an updated page anymore (till refresh but than the same goes for client B they don't get an error because of the catch that I use).
Is there a way for every client to keep connected to the database that is needed for that page or pages? So that when client C goes to another page that uses either database Z,Y or maybe even X that they don't interfere with each other?

If there is a tutorial available somewhere please let me know. I've tried a few but couldn't implement it in Blazor server side. If it is not possible let me know as well.
Thanks in advance

Answer 1

Is there a way for every client to keep connected to the database that is needed for that page or pages?

Not the web client accessing the database, it's the blazor backend and web backend normally work stateless = no permanent connection.

If it is not possible let me know as well.

Indeed; you have to rethink your application design.

Answer 2

Unlike regular websites, blazor server apps have dedicated state, tied to the signal/r connection, but not a dedicated thread.

So, there is no technical reason your code won’t work. It sound like you are not managing the database connections properly.

Answer 3

You would not have (or need) a separate database for each user.

All your users would use the same database. For a tutorial see: Creating A Step-By-Step End-To-End Database Server-Side Blazor Application (updated to .Net 6)

You can open up the app in multiple web browsers, and create and log in as different users.