Are there any heuristics to define server requirements for typical applications? Coming from internal development to a handful of users, this is our first deployment of a internet application. Internally, we just deploy, monitor and act if needed, but being on a tight budget and having to deploy remotely, I have to do a estimate with a greater degree of accuracy.
I have the following sources of input to a parametric estimate:
Out of testing I get: - the trafic volume - the number of SQL requests
And from the project management I get the number of expected total and simultaneously connected users.
Is there a rule of thumb that I can apply on these parameters?