Chattanooga
Unix
Gnu
Android
Linux
Users
Group

 

Hot Topics:

Sponsoring:

AWS Reliability

From: Eric Wolf 
------------------------------------------------------
Y'all,

I recently set up a client on AWS. They have a simple LAMP setup with very
little traffic but just high memory needs. In the ensuing month, we've
experienced several failures including a hardware failure on an EBS volume.

Is this the norm for AWS? Or should I be looking at Rackspace or just
colo-ing my own box?

-Eric

-=--=---=----=----=---=--=-=--=---=----=---=--=-=-
Eric B. Wolf                           720-334-7734

=============================================================== From: wes ------------------------------------------------------ I wouldn't call it the "norm" - I have over 50 instances on AWS EC2, many making use of EBS volumes and other AWS features like RDS and Elasticache. They generally work fine most of the time. That said, I have had far fewer failures and usually lower prices on Rackspace Cloud. Additionally, I have noticed Rackspace to be generally responsive and cooperates with the community. Amazon, on the other hand, has on occasion been difficult to work with on several points and not always responsive to community demands. It's REALLY hard to get an email out from an EC2 instance without it being flagged as spam. Plus, Rackspace does less shenanigans with network traffic. Downside with Rackspace is they have fewer features, but for a simple setup like you describe, this should not be a problem. -wes

=============================================================== From: Sean Brewer ------------------------------------------------------ I'll put it this way, if there was a PaaS like Heroku that used Rackspace instead of AWS, I'd switch in a heartbeat.