: You're going to need more details than just the number of concurrent users. What web services do you need (PHP, ASP, static files, database, which database, cache layer, etc...)? Some of

@Rambettina238

You're going to need more details than just the number of concurrent users.


What web services do you need (PHP, ASP, static files, database, which database, cache layer, etc...)? Some of this will
What level of redundancy/availability do you want? Higher availability means less potential down time but at an expense of higher cost, time, and skill to setup.
What is the average request rate for a user of the site? Look at static files, dynamic files, database requests, what can be cached and what can't.
Do some quick tests/benchmarks for various systems to get a rough idea of what capabilities they have. Even better would be a simple prototype game setup which simulates the kind of requests you expect.
If you're completely unsure just start with cheap/basic hardware and perform benchmark testing when you application gets to a minimally usable level. With a good design and setup you'd be surprised how much a low end server can do. Design and plan the system for easy migration to more powerful hardware if/when you need it.

Vote Up Vote Down

Login to post a comment!