Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« Meet me in Provo Next Week! | Main | Upcoming Conferences - Spring 2007 »


TrackBack URL for this entry:

Listed below are links to weblogs that reference Avoid the Crunch, go Web-Scale:


Feed You can follow this conversation by subscribing to the comment feed for this post.


You are late to the party Jeff. People used to visit TC at some point of time for news. Not anymore. Stale stories don't amount to much.


Maybe I'm missing something about EC2, but the fact that you have to externally load-balance web requests defeats the purpose for me. Even though the load on the load balancers is less than actually handling the traffic, you're essentially double paying for bandwidth, and adding latency. The inability to do this inside the EC2 environment makes it virtually useless for web request processing like this.

Phil Wolff

While I appreciate the shoutout, I can't claim credit for that suggestion. Perhaps the commenter before or after mine?

Carolynn Duncan


Paul Allen recently blogged about how AWS will be helping World Vital Records with scalability... and I agree:

I'm not technically a geek, but even so, EC2 and S3 are constantly on my mind as something I think is awesome. Way to be. :)

Paul Bissett

We have found that EC2 is viable for auto-scaling our server needs including handling spike, as well as cyclical traffic, requirements.

We had to overcome some critical issues such as dynamic IP addressing coupled with a lack of a 24/7 service level agreement. However, we have solved these issues for our own application at Weogeo, and we will begin to offer this EC2 management AMI, called WeoCEO, as a private beta product for developers of AWS applications.

The WeoCEO application, working within the EC2 environment maximizes the power of EC2 by providing automatic and instantaneous scaling, load balancing, and fail-safe supports, within a stable IP environment.

Alex Kerr

> Build using Amazon EC2 and S3.
> Use a load-balanced architecture

Yes, but how do you actually DO that??? If I've got my standard LAMP architecture on a server somewhere - Apache with ModPHP and a PHP script talking to a MySQL database, can anyone tell me exactly what I have to do to rearchitect that to mork on a multiple EC2 instance scenario? i.e. specifically how do I keep data consistent and accessible between mutliple MySQL installations in real time, how do I shrink and increase the number of EC2 instances? How do I load balance the site if it's hosted on multiple EC2 instances? We need real facts please!

The comments to this entry are closed.

Featured Events

The AWS Report

Brought to You By

Jeff Barr (@jeffbarr):

Jinesh Varia (@jinman):

Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30