Skip to content

Blazor Server-Side Question & Discussion - # of server instants running... #11945

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
BenHayat opened this issue Jul 7, 2019 · 1 comment
Closed
Labels
area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Duplicate Resolved as a duplicate of another issue

Comments

@BenHayat
Copy link

BenHayat commented Jul 7, 2019

Hi guys;
Looking at the pros & cons of server-side hosting model, one area that concerns us, is that, for every user that launches our app, a new copy of our app gets instantiated along with two other class libraries for Data Access and Business Domain.

The questions are:

  1. Does every instance take up the same amount of resources as the first instance?

  2. Since we don't know how many people come to the site, how do we know, when there are too many instances are alive?

  3. When does an instance go away and resources are returned? Is there a session timeout if user is inactive?

  4. What's the best strategy to keep an eye on this and not let the system crash?

Thank you in advance!
..Ben

@mkArtakMSFT mkArtakMSFT added area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Duplicate Resolved as a duplicate of another issue labels Jul 8, 2019
@mkArtakMSFT
Copy link
Member

Thanks for contacting us, @BenHayat.
We plan to resolve/provide answers to these questions as part of #10472 work.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Duplicate Resolved as a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

2 participants