Amazon Web Services Arfchitecture and Costing -


i extremely new amazon web services. sincerely appreciate on finalising architecture , arriving @ costing schedule. working on designing aws based solution dynamic website designing. begin need have 2 high cpu medium utilisation ec2 instances (both act web servers), 1 high cpu medium utilisation ec2 instance database postgre sql , 1 high cpu medium utilisation ec2 instance serve read replica database. having considerable volume of static content images, videos or .doc files contemplating using s3 bucket. so, website dynamic + static kind of website. expecting rapid exponential scale of users 0 example 1 million in year. hence need scale ec2 combos (as described earlier) according traffic. contemplatng using cloudformation stack rapidly scaling deployment. also, efficiently route traffic using single elb start with. also, want vertically partition database based on user id's. example, user id 1 - 2000 on 1 ec2 database instance users 2001 4000 on second ec2 database instance etc... auto scaling web server ec2 instances while database ec2 instances have 100% uptime

my questions are:

  1. what should auto scaling strategy web server ec2 instances , how know monthly costing when scaling dynamic. mean there way predict can cost break analysis?
  2. do ec2 instances (web server , database) need ebs backing or ephemeral storage suffice? believe database ec2 instances need ebs backing. web server ec2 instances?
  3. suppose end scaling 100 ec2 instances. 1 elb suffice or need multiple elbs?
  4. how analyse how many http requests can 1 high cpu medium utilisation ec2 instance handle before breakdown?
  5. can cloudfront used host kind of dynamic + static site or used static sites?

please me these questions have no clue on cloud solution architecting...

thanks... vikram.

a quick attempt @ answer started;

  • #1 big answer without writing book, has system , design answer in generic way.
  • #2 you'll want backing database. web servers on other hand better off ephemeral storage, more stateless/setup free are, easier create/destroy instances dynamically.
  • #3 far know, there's no upper limit on number of machines "attached" single elb. under extreme load, may experience lesser latency if split site on multiple load balancers. you'll find more info can map against actual architecture here.
  • #4 load testing of system can tell that.
  • #5 cloudfront page;

amazon cloudfront can used deliver entire website, including dynamic, static , streaming content using global network of edge locations.

in other words, architecture not prevent mixing static , dynamic content on site.


Comments

Popular posts from this blog

html5 - What is breaking my page when printing? -

c# - must be a non-abstract type with a public parameterless constructor in redis -

ajax - PHP/JSON Login script (Twitter style) not setting sessions -