jeudi 3 septembre 2015

Amazon AWS how to configure servers to scale?

I'm fairly new to amazon, not to Linux, routing, web serving/hosting. So please be patient with me and my novice AWS questions.

The company I work for has a team building an application that they don't want hosted internally and are pushing to AWS. I have played with and configured a couple hosting servers in AWS but not to this complexity. I understand VPC and EC2 and have working knowledge of S3.

I have searched through the web, but no where does it detail how the scaling part works, and I'm not talking about automated scaling. I'm interested to know how the actual server configuration works.

For instance, we have a jar file and properties files that need to be deployed to a server in order to have a running site. The questions is, where do I place these files, so that if I wanted to scale to another bigger or smaller resource instance, it would use those same files? My research seems to be pointing to "EBS" and S3 for this setup, but I'm not to clear on how... I guess the question is, how do I configure instances to read site files?

My question is presuming that at any given point I have one instance running and reading the site files, and if I wanted to use a bigger instance or a smaller instance I would shutdown the current instance and boot up a new instance, of course, while always reading from the same site files..

My scenario may not be the correct way to create a scalable architecture, so if you have a better suggestion, than I'm all ears. This is how I've understood the scalable aspect of AWS works. And keeping in mind I'm using the scaling up or down approach and not the scaling out, which scaling out suggests having more than one instance running in order to balance computation between instances and increasing the cost by instances running..

Clarity would be greatly appreciated!




Aucun commentaire:

Enregistrer un commentaire