EC2, EBS and RDS are all down on US-east-1.
Edit: Heroku, Foursquare, Quora and Reddit are all experiencing subsequent issues.
EC2, EBS and RDS are all down on US-east-1.
Edit: Heroku, Foursquare, Quora and Reddit are all experiencing subsequent issues.
If you actually wish to make a useful point about the practicality or otherwise of massively virtualised systems for webapp deployment, please do. It's going to take more than two words though.
If you actually wish to bitch about a post that we all got the point of, you're going to need more than two paragraphs.
Anyway, my bad, I was just trying to make a joke to lighten up the mood. Sorry.
So I guess that is the long way of saying that hopefully it won't happen again.
1. Sharding data 2. Pulling tables out to other servers from the main DB 3. Pruning excessive data 4. Compressing data
Doing things the right way with EC2 means using EBS. It's the brake caliper to the rotor. Sure you could have drum brakes but they're not nearly anywhere effective as they quickly get heat soaked. I'm referring to S3.
One should trust ephemeral storage. Your instance can go down at anytime. Write speeds to S3 are not nearly as fast as ephemeral or EBS arrays (raid).
Hate to say it, but If one cannot trust EBS then what the heck are 'we' doing on EC2... EBS quality should be priority one, otherwise we're all building Skyscrapers on foam foundations of candy cane rebar.
We have had a lot of success stabilizing EBS by creating mdadm arrays out of lots of smaller EBS volumes. There is minimal additional costs and you can get better performance, stability, and protection (RAID 5, 6).
Gluster makes an OSS distributed filesystem that runs across availability zones, our AMI (not OSS) builds multiple RAID arrays on each instance then spreads the filesystem across instances in multiple AZs. Send me an email if you want to chat.
It's hard to tell for sure since there isn't any load.