4 ms·

Using AWS doesn't magically make your application 'scale'. You still need to architect it in such a way that you can add additional resources (app server, db se

by joshwa 19y ago

Using AWS doesn't magically make your application 'scale'. You still need to architect it in such a way that you can add additional resources (app server, db server, web server, etc) to accommodate your load. What AWS (or slicehost/other VPS) does take care of is the server provisioning/bootstrapping process-- if you have images set up for each of your server roles, you don't have to go through the headaches of calling up your server company, ordering servers, doing burn-in testing, etc. You just whip out your CC, and 10 minutes later you have a working server. (or, in the case of AWS, you can automate the whole provisioning process and scale in near-real-time according to load) For your situation, where you're hosting domains, you probably want to have one or more frontend/"master" boxes hosting the domains, but internally forward the traffic to whatever server is actually hosting that instance of the app.

izak30 19y ago
I wouldn't suggest that anything is 'magic' about any web service, and AWS is just an example, This is more of a web theory question. Most startups with low funding start out on cheap servers and then scale to multiple cheap servers (google), if that is the right answer, then multiple (gs) accounts could be better than a single (dv) acct or even multiple AWS accounts, but if there is something about another service that makes Scaling easier with that service, or if there is some way that you architect your program so that you can easily scale across multiple servers (and not just have multiple instances of the program on multiple servers), i.e. to divide as necessary rather than to pre-divide your resources, is that the way to do it from the start, or does everybody start very very small?
- joshwa 19y ago
  >if there is some way that you architect your program so that you can easily scale across multiple servers (and not just have multiple instances of the program on multiple servers) See this article: http://highscalability.com/unorthodox-approach-database-design-coming-shard http://highscalability.com/unorthodox-approach-database-desi... In fact, see that whole site. There's a lot of stuff there.
  - izak30 19y ago
    Thanks.

by joshwa 19y ago

izak30 19y ago

I wouldn't suggest that anything is 'magic' about any web service, and AWS is just an example, This is more of a web theory question. Most startups with low funding start out on cheap servers and then scale to multiple cheap servers (google), if that is the right answer, then multiple (gs) accounts could be better than a single (dv) acct or even multiple AWS accounts, but if there is something about another service that makes Scaling easier with that service, or if there is some way that you architect your program so that you can easily scale across multiple servers (and not just have multiple instances of the program on multiple servers), i.e. to divide as necessary rather than to pre-divide your resources, is that the way to do it from the start, or does everybody start very very small?

joshwa 19y ago
>if there is some way that you architect your program so that you can easily scale across multiple servers (and not just have multiple instances of the program on multiple servers) See this article: http://highscalability.com/unorthodox-approach-database-design-coming-shard http://highscalability.com/unorthodox-approach-database-desi... In fact, see that whole site. There's a lot of stuff there.
- izak30 19y ago
  Thanks.