Re: Give me some of what he's been drinking
"Cloud comes at a high cost not only in dollars, but in complexity and uncontrollable downtime. "
AWS has never gone down in its 16 yr history. There have been service outages, a few notable ones as well. There have even been whole regions that have been down, but once or twice in history, for a few of hours. Service outages are regional, not global. There are some global services, but the global aspects of the services, for example, IAM, are the control plane operations, not the data plane. So if IAM has a global outage, you can't create new users, but you can continue to authenticate in the region you operate in.
High availability in somewhere like AWS is a tick box for some services, like RDS SQL. Ticking the box creates a new replica in a new Availability Zone, configures and monitors synchronous replication and auto recovers from failure. A different tick box spins you up a read replica in another region. In other services, HA comes out of the box, like S3, where when you store an object, the underlying control plane replicates the object to three Availability zones as standard. Each AZ is miles apart, with independent power, cooling, network, and transit centre. Ticking the box allows you to replicate S3 buckets to a different region.
It's a lot simpler to have Highly Available workloads than trying to do this yourself. AWS recommends you design for failure; they have a well-architected tool to help you and make you think. There are many reasons to argue against Cloud, I argue that Availability is a plus for Cloud, not a detractor, it's so easy to make your workloads span multi-AZ Multi, Multi Region there is no excuse other than paying hard-earned cash for the privilage.