4 ms·

There is also (and especially if your a small shop) the thing where if your self hosted stuff goes down, you have a crappy time fixing it, over weekend, holiday

There is also (and especially if your a small shop) the thing where if your self hosted stuff goes down, you have a crappy time fixing it, over weekend, holiday, etc, until its done. If AWS goes down, thousands of other people are working on it frantically. And most likely, many of them are smarter/better than you.

tlarkworthy 6y ago
Single tenancy systems are simpler and avoid neighbourhood noise and safety limits.
mattmanser 6y ago
So this just happened to a friend of mine who used managed.com, which was down for a week last week because of a ransomware attack. Didn't really get mentioned here, but that was a lot of websites. Instead of stressing about getting his sites back up, he was stressing that he'd never get any of his data or code back and that he couldn't contact his 100,000s of users because he didn't even have a recent backup of the database with all of the emails. Even his DNS settings went down as those sort of sites push you to making them the nameservers. I ended up telling him about wayback machine just so he could get a homepage set up. He'd relied on their claims that they managed his backups for him, but when they went down, it took down his ability to even access the backups, and they wouldn't do anything, I assume in case those backups were infected too. So in fact if you're blindly relying on an external provider, it's even more risky than hosting yourself. At least the stuff you self host you are almost pushed to back up to something like S3, and both won't go down.
- hunter2_ 6y ago
  The entire premise of claiming to have backups is that you are the fork who ensures multiple copies have no commonalities, no overlap, in what keeps them healthy. You can delegate if you aren't interested in DIY and getting in the trenches, but you still need to apply the original premise by being a fork and delegating to multiple separate entities... Otherwise, you can't claim to have backups, despite the fact that the one basket you put your eggs in can legitimately claim to have backups.

tlarkworthy 6y ago

Single tenancy systems are simpler and avoid neighbourhood noise and safety limits.

mattmanser 6y ago

So this just happened to a friend of mine who used managed.com, which was down for a week last week because of a ransomware attack. Didn't really get mentioned here, but that was a lot of websites. Instead of stressing about getting his sites back up, he was stressing that he'd never get any of his data or code back and that he couldn't contact his 100,000s of users because he didn't even have a recent backup of the database with all of the emails. Even his DNS settings went down as those sort of sites push you to making them the nameservers. I ended up telling him about wayback machine just so he could get a homepage set up. He'd relied on their claims that they managed his backups for him, but when they went down, it took down his ability to even access the backups, and they wouldn't do anything, I assume in case those backups were infected too. So in fact if you're blindly relying on an external provider, it's even more risky than hosting yourself. At least the stuff you self host you are almost pushed to back up to something like S3, and both won't go down.

hunter2_ 6y ago
The entire premise of claiming to have backups is that you are the fork who ensures multiple copies have no commonalities, no overlap, in what keeps them healthy. You can delegate if you aren't interested in DIY and getting in the trenches, but you still need to apply the original premise by being a fork and delegating to multiple separate entities... Otherwise, you can't claim to have backups, despite the fact that the one basket you put your eggs in can legitimately claim to have backups.