How do I update my asp.net app to support more users?
When the asp.net website has about 1000 active users, it works well.
How can I do if my website has about 100,000 active users?
How do I update my asp.net app to support more users?
Changing the webApp architecture?
Or buy more web servers?
I'm just wondering, in the real world, how do other people build an asp.net site that supports millions of users? What is the architecture of a website application to support?
Any suggestion would be greatly appreciated.
source to share
First, make sure you have your first hosting provider.
Second, download the performance profiler (I always suggest the Red Gate Performance Profiler ) and your application profile. Find bottlenecks and fix them. Repeat until you get the desired performance metric.
source to share
You say it "works well" at the moment. It is impossible to understand at what point this moment may change, it will not know much more about the nature of your traffic, the current setting, what else is running on the server, etc. Etc. Maybe it continues to "work well" with a million users as it is.
Whenever you need to make changes (and slow performance degradation will alert you), you need to worry. And then, as Justin says, knowing the potential bottles will give you directions as to which solution you need.
source to share
Buying more servers is one strategy. This is how architecture changes. The easiest and most economical way is to throw more servers at it. It depends a little on the current architecture of the application, but nothing can be easily overcome.
I suggest downloading the test app. See what happens when you increase your active users. Who knows it can handle 100,000 active users, it may not be, but at least you know the tipping point.
As far as what you have to do, it really depends on the needs of your business. If your company has $$ and it is a core product then a robust application architect makes sense. If it isn't, perhaps throwing hardware into the problem is good enough.
It will also help if you can identify the active user. Is this someone visiting your site and conducting a session? That's 100k concurrent requests to the server ...?
source to share