Blazor [1] has a concept of "circuits" [2] where each connected browser has a corresponding instance on the server. It's part of the reason why I personally do

Blazor [1] has a concept of "circuits" [2] where each connected browser has a corresponding instance on the server. It's part of the reason why I personally don't like it being recommended for simple CRUD apps (brings back memories of webforms) as it doesn't seem very "webby", but this makes a great point that for some kinds of apps it's the best or at least a very advantageous model. It's great to grow terminology and maturate platforms so that we can recognize and then adopt appropriately. [1] https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blazor https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blaz... [2] https://docs.microsoft.com/en-us/aspnet/core/blazor/state-management https://docs.microsoft.com/en-us/aspnet/core/blazor/state-ma...