Currently I have one server that runs an ASP.net web application (on IIS) and this is also running a SQL Server database.
I am getting more and more traffic and soon I will need to increase the amount of traffic I can handle so the user experience is not compromised. I am not talking about google or amazon type traffic.
My question is, what is a realistic network and server layout to provide me with better performance and big me a reasonable about of redundancy without expecting to pay huge amounts of money.
I would like to keep down time to a reasonable minimum but am not expecting a 100% available all the time solution.
I was considering something like a firewall, loadbalancer, two web servers running IIS and one SQL server with a reasonable spec (maybe a Dell R710 with 16GB or more ram), and possibly a second SQL server that we can cluster to the other one.
I would like the system to be able to scale in such a way that if in a year or two we have increased our traffic dramatically, we can add additional servers to cater for the increased traffic without rebuilding the entire system.
Any suggestions or links pointing me in the right direction is perfect.
Note: I have been going through highscalability.com but most of these case studies and articles are referring to mega sites like StackOverflow, Amazon and other super huge site with giant volumes of traffic. I am not in that boat yet.