4 ms·

To me this is a fallacious argument. Dedicated servers are wildly cheaper than RDS/AWS. Isn't that the whole point of AWS? To have a team of experts managing

To me this is a fallacious argument. Dedicated servers are wildly cheaper than RDS/AWS. Isn't that the whole point of AWS? To have a team of experts managing your hosting to prevent a failure like this?

PaulHoule 14y ago
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.
- huggyface 14y ago
  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.
  - purephase 14y 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.
  - count 14y 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.

PaulHoule 14y ago

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.

huggyface 14y ago
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.
- purephase 14y 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.
- count 14y 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.