Forum Moderators: phranque
I'm planning to open new site, and want to include in my plans
scaling if site become popular.
So i think of 3 ways.
Google App Engine, Amazon AWS with SimpleDB, or virtual private server.
VPS is obviously the cheapest for bandwith etc, but if site grows big then probably i would pay for someone that will do the scalling to new servers, so i might pay more at the end.
Google App Engine and Amazon AWS are created to what aim at easy scaling. Google App Engine is not in commercial mode yet.
What do you think of advantages and disadvantages for this solutuions?
Or maybe other way that i didnt wrote about?
If you're a big forum-based site then you'll have very different scaling issues compared to a site with mostly static content.
If you're going to have dymanic content, whose code are you planning to use? If you're buying e.g. a commercial CMS, then the supplier should be able to provide detailed info on scaling. If they can't/won't, perhaps you should find an alternative supplier.
but if site grows big then probably i would pay for someone that will do the scalling to new servers, so i might pay more at the end
What's your definition of "grows big"? 1,000 visitors a day? 1,000,000 visitors a day?
Content will be rather static type. Users Will input little and rarely
but there might be a lot of users (about 100mln).
My definition of big is about 20-30mln visits per month,
so that would be about 1,000,000 per day.
If site will become big it will have very big database,
so most crucial part will be search and retrieving from DB.
Site will be coded from scratch so no commercial code will be included.
As i understand, LinkedIn uses Java, Oracle & MySql, and Lucene.
I'm not familiar with Java. I guess that Java programmers would be
more expensive then PHP or Python programmers, because
Java is less popular.
I would like to start with good assumptions rather then,
re-coding whole site later.
All suggestions are welcomed.
