Take the 2-minute tour ×

I was wondering what would be the route for expansion in this case?

Let me explain. I wrote an ASP.NET web application that acts as an API server for a client program that runs on all types of devices (from smartphones to tablets to Windows clients.)

This ASP.NET web app runs on its own machine on Windows 2008 Server, that is connected to a single machine that runs SQL Server 2008 database.

Everything used to work fine, except recently we've started getting issues with SQL server being inundated with queries and the IIS itself started to run "hot" with all the requests. We did the analysis and it turns out that there's about 10,000 client devices that may be connecting to this ASP.NET server.

So what is the hardware expansion that needs to be done to accommodate this larger demand that we expect to increase in the future?

share|improve this question
Think about rearchitecting now to support better scale-out. It sounds like you didn't have a scaling model in mind when designing the app in the first place - now's the time to develop and move to a better model, before you run out of scale-up potential. Think / look at Azure, Amazon, etc. In the meantime, maybe you can tune the queries and implement more intelligent caching at the IIS layer, but eventually you're likely to run out of vertical road, and have to scale by number of boxes, app partitioning, and Clever Things, not just more cpu etc. –  TristanK Mar 18 '13 at 4:06
add comment


Your Answer



Browse other questions tagged or ask your own question.