4 ms·
Because the cloud remains the same? All of what you mention is something you consider during install. Which arguably makes the install take most of its time.
by tjoff 4y ago
Because the cloud remains the same?
All of what you mention is something you consider during install. Which arguably makes the install take most of its time.
Same should be true for the cloud. Because you surely are not just jumping into something without analyzing what you are locking yourself into etc.?
Yes, it sucks if your PSU goes into smoke at an inopportune time. So you don't put critical services on it. Just as you don't on the cloud either. AWS has a much worse uptime than my homeserver. Github, slack, netflix, etc too.
Also, you get to do maintenance when you know noone will be bothered by it.
- floatinglotus 4y ago“ AWS has a much worse uptime than my homeserver.” I find this extremely hard to believe.
- bsagdiyev 4y agoI absolutely do not. I see AWS outages and issues with provisioning all the time at work. Last time my home server went down was because the power went out and we don't have a generator.
- wkdneidbwf 4y agoi think what gets lost here is how we’re defining uptime. if you’re regularly experiencing ec2 outages that result in your apps and services being unavailable i find it very hard to believe you’re using ec2 correctly. running a bare one-off ec2 instance on aws is a strange choice if you care about uptime.
- wkdneidbwf 4y agothe statement doesn’t even make sense. “aws” isn’t a single service and measuring uptime across every aws service is nonsensical. obviously they mean ec2, but even then lumping all regions and azs together is weird.
- deleted 4y ago[deleted]