I should rephrase it as "That if the product is going to be internet enabled, servers should be in-house."
I should rephrase it as "That if the product is going to be internet enabled, servers should be in-house."
When AWS goes dark it's news. When some company's server room goes offline some IT tech gets a pizza paid for by the company and a bit of a late night
When AWS goes dark, pray and go grab a coffee, there is nothing you can do.
Keep pressing refresh on aws status page.
Having control is great when someone's breathing down your neck, but for a lot of organizations you'll not have people breathing down your neck as often on AWS. (At least in terms of the service itself, bad code and bad deploys are still a thing)
It's different tradeoffs and the vast majority of shops are not set up to compete with AWS in terms of uptime.
I'm not an AWS apologist by any means and in fact I've been moving services off AWS over the last few years, but I can't abide your claims of FUD.
Experience. The pizza thing is a thing I used to do (far too frequently) lmao