4 ms·
Even ignoring labor, none of these analyses ever consider BC/DR or backup costs. S3 for backups is the single biggest ease-of-mind feature AWS provides, IMO.
by bpodgursky 6y ago
Even ignoring labor, none of these analyses ever consider BC/DR or backup costs.
S3 for backups is the single biggest ease-of-mind feature AWS provides, IMO. I do not want all my data sitting in a single colocation facility without backups.
If I run a database on RDS, maybe it costs more than a bare-metal server, but I can replicate the automatic hourly backups to as many regions as I want. Incredible peace of mind over a self-managed facility.
- Patrick-STH 6y agoThose are included in our colo costs with a second data center where we have a smaller DR cluster.
- teh_klev 6y agoIt never fails to amaze me how many HN contributors don't seem to read the linked articles yet seem compelled to tell you off for things you've already accounted for, explained and justified.
- bpodgursky 6y agoThere's absolutely nothing in the article (which I did read) about it. If you yourself had read the article, you would know that it was not explained, accounted for, or justified. There is a single vague reference to a "primary DC". There is no discussion at all of backups or disaster recovery.
- renewiltord 6y agoMind quoting the section in the linked article that accounts for this, explains it, and justifies it?
- mekster 6y agoIt's because comments are usually far more intelligent and interesting to read and I set my app to open up comments than the story by default. I don't blame the others doing the same.
- teh_klev 6y agoSo how can you comment on, or have a critical thought about an article, if you're just reading a bunch of other comments likely left by others who also likely didn't read the article? I find that genuinely baffling, and somewhat worrying, especially on more serious topics.
- renewiltord 6y agoBro, you didn't read the article and you're leaving comments so I think maybe you don't find it that baffling or worrying.
- teh_klev 6y ago"Bro" I sure as hell did and even watched the video. There's enough in there to read between the lines that they've got a DR solution. And to be honest the amount of nit-picking by AWS/Cloud fanbois is verging on comical.
- renewiltord 6y agoDon't even try. It's obvious you didn't. And I use GCP, homes.
- teh_klev 6y agoAnd well done for you, I use Azure. Let's give us all a pat on the back.
- rsync 6y ago"S3 for backups is the single biggest ease-of-mind feature AWS provides, IMO. I do not want all my data sitting in a single colocation facility without backups." I'm biased, but in my opinion if your infrastructure is on AWS and your backups are on AWS you're doing it wrong. Even accounting for zones and geo-disparity, etc. Luckily: ssh user@rsync.net rclone s3:/some/bucket /rsync.net/home ... which is made possible by rclone[1], which is excellent, and the fact that rsync.net has rclone built into the remote environment[2] such that you can execute it over SSH. [1] https://rclone.org/ https://rclone.org/ [2] https://www.rsync.net/products/rclone.html https://www.rsync.net/products/rclone.html
- mekster 6y agoMaybe just take a few days and learn how to do backup with a few simple commands? Fortunately we have tools like borg that is stable and does your backup encrypted easily. My mind only rests when I have my data encrypted locally before being sent and are put on different providers and regions. Cost of not trying to learn because clicking seems easy is a cost by itself.