what's the number of times the letter "t" appears in:
q: ec2 cost-effective webapp scaling i have a webapp running in a media temple vps account, and i'm currently evaluating the gains to switch to amazon ec2. it's running under apache 2 web server.
this webapp for now has almost no access normally, with some big utilization peaks, which are known with some days of notice.
right now at media temple we have a server with 2gb of memory, which is enough for those big utilization peaks. as we move to amazon, i'm thinking maybe of having two instances - a micro for normal use, and a small or even medium for the peaks.
i'm trying to figure out the best way to do this in a way this could work. at first, i could maybe change the dns, routing the clients to the bigger server when those peaks come. but this would be quite dangerous in my opinion, so i'd like to know how this can be done correctly.
thank you!

a: the canonical way to do this is to have multiple application servers behind a load balancer (which, if you're on aws, could be their load balancer product, elb). this way, you can scale the number of app servers up and down on demand. this is generally referred to as horizontal scaling. 
whether or not this will work with your application is something you'll need to figure out. implementing multiple app servers may require some re-engineering on your part. 
if it won't work, then you're typically stuck with vertical scaling(increasing and decreasing resources on a single machine), which is not nearly as easy to scale up and down. 

a: amazon provides a couple services that would help you to do this:


*

*elastic load balancer to balance incoming load across one or more services (ie apache answering port 80)

*cloudfront cdn to cache and distribute as much of your static content as you wish

*elastic beanstalk to scale your setup automagically


you won't have to change dns, you can just add servers to the pool when you need them and remove them when you're done.
edit: just saw the question in comment above: testing in aws is easy, you can spin up a couple servers and a load balancer in a matter of 10 minutes or so and try it out.

user
In the text, there are 127 "t"s.
assistant