undefined | Better HN

0 pointsPaulHoule14y ago0 comments

I find it's very expensive to talk with salespeople to get my dedis configured properly. Particularly when they screw it up anyway.

The reason I moved to AWS was because when I added a new (cheap) hard drive to my dedi, they didn't put a partition table on the disk. When the machine rebooted, the superblock got overwritten and I lost access to the file system. (I did manage to recreate the superblock and get the data out, but jeese...)

One time I made a ticket and somehow my record in the trouble ticket system got screwed up and I couldn't put more tickets in. Some wizard fixed that in the SQL monitor after I talked to 3 other people who had no idea this could happen.

As for costs it's not so simple. I've got a processing job I run each week that costs $6 of CPU time because I pay just for what I need. I wouldnt want to run it on a dedi because it's a beast.

0 comments

3 comments · 1 top-level

huggyface14y ago· 2 in thread

Your anecdote is interesting, but not relevant. The parent rightly observes that the whole point of a service like RDS is that you don't have to babysit it. If you still do then it's all of the disadvantages of your own box, plus more disadvantages.

count14y ago

You don't though, as noted above. If you checked the 'multi-az' check box, which costs a little extra, then everything worked properly.

If you cheaped out and used a single-AZ deployment, against published best practices, than it's your own damn fault.

purephase14y ago

Admittedly, I'm not that familiar with RDS, but I think there is a big difference between babysitting and common practices around data protection.

Always plan for failure regardless of where your data is, what claims are made, or how much you're paying.

j / k navigate · click thread line to collapse