Re:Amazon RDS failure - data has been lost
by kennu on Friday June 15, 2012 @09:26AM
(#4116329)
What would you recommend for persistent disk storage on AWS instead of EBS then? Assuming you need to put database files somewhere where they don't disappear when instances terminate, and your database can access them.
[ Parent
| on HN ]
The Netflix approach (which definitely isn't for everyone), is to use no persistent storage.
They cluster their databases across multiple instances, availability zones and regions, and back them up constantly to S3. Their ultimate recovery plan is to restore from backup if necessary, which is pretty much the same as assuming EBS will corrupt your data.
While it's far from trivial to do it that way, they seem to be the most successful user of the AWS systems.
Re:Amazon RDS failure - data has been lost
by semanticist on Friday June 15, 2012 @01:02PM
(#4117446)
I'm more and more of the opinion that EC2 only makes sense for very small (2-3 node, no significant load) or very large (Netflix) deployments, and almost everyone else would be better off with either Linode-style VM rental or actual dedicated servers, depending on their needs.
The only exception I've seen are people with very spiky traffic patterns, who can save a bit of money by only running instances when they need them - but even then I suspect that the money saved might be less than you'd think.
Re:Amazon RDS failure - data has been lost
by bluestix on Saturday June 16, 2012 @04:15AM
(#4120135)
For any constant load applications dedicated servers are definitely much cheaper then ec2.
Amazon wins for APIs and convenience but not for price.
You use EBS and back it up using the built-in snapshot functionality, and/or back it up another way. RDS, which is presumably based on EBS, provides backups and snapshots for precisely this reason.