When your cheap dedicated server goes down and your admin is on holiday and you have hundreds of angry customers calling you, you'll get it.

Or you need to restore your Postgres database and you find out that the backups didn't work.

And finally you have a brilliant idea of hiring a second $150k/year dev ops admin so that at least one is always working and they can check each other's work. Suddenly, you're spending $300k on two dev ops admins alone and the cost savings of using cheaper dedicated servers are completely gone.

> When your cheap dedicated server goes down and your admin is on holiday and you have hundreds of angry customers calling you, you'll get it.

Or when you need to post on Hackernews to get support from your cloud provider as locked out of your account, being ignored and the only way to get access is try to create as much noise as possible it gets spotted.

Or your cloud provider wipes your account and you are a $135B pension fund [1]

Or your cloud portfolio is so big you need a "platform" team of multiple devops/developer staff to build wrappers around/package up your cloud provider for you and your platform team is now the bottleneck.

Cloud is useful but it's not as pain free as everyone says when comparing with managing your own, it still costs money and work. Having worked on several cloud transformations they've all cost more and taken more effort than expected. A large proportion have also been canned/postponed/re-evaluated due to cost/size/time/complexity.

Unless you are a big spender with dedicated technical account manager, your support is likely to be as bad as a no name budget VPS provider.

Both cloud and traditional hosting have their merits and place.

[1] https://arstechnica.com/gadgets/2024/05/google-cloud-acciden...

It is statistically far more likely that your cloud service will go down for hours or days, and you will have no recourse and will just have to wait till AWS manage to resolve it.

After 8 years operating like this, I have had approximately the same number of critical outages in standard Cloud as with these providers.

One included a whole OVH building burning down with our server in it, and recovery was faster than the recent AWS and Cloudflare outages.

If you want to, these providers also offer VMs, object storage and other virtualized services for way cheaper with similar guarantees, they are not stuck in the last century.

And I don’t know how people are using cloud, but most config issues happen above the VM/Docker/Kubernetes level, which is the same wether you are on cloud or not. Even fully managed database deployments or serverless backends are not really that much simpler or less error-prone than deploying the containers yourself. Actually the complexity of Cloud is often a worse minefield of footguns, with their myriad artificial quirks and limitations. Often dealing with the true complexities of the underlying open-source technologies they are reselling ends up being easier and more predictable.

This fearmongering is really weakening us as an industry. Just try it, it is not as complex or dangerous as they claim.

That's even worse when AWS goes down and myth of it never going down should be more than shattered by now

Sure, but AWS has more downtime than I do :-)

What prevents an EC2 instance from going down in exactly the same way? Other hosting providers offer automatic backup too - it's not an AWS exclusive feature.

When your system goes down on AWS and your AWS admin is on holiday, you'll have the same problem.

What is your point?