this post was submitted on 02 Aug 2025
372 points (97.2% liked)
Programming
21961 readers
131 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The author put it well:
Multi-region cloud computing is already difficult and expensive enough, multi-cloud is not only technically complex but financially and legally fraught with uncertainties. At that point you're giving up so much of the promise of cloud computing that you might as well rent rack space somewhere, install bare-metal infra, and pay someone to drive there to manually backup to tape every 3 months.
This level of technical purity is economically unfeasible for virtually everyone, that's the whole point of paying a vendor to deal with it for us. And you know who doesn't need to put up with the insane overhead of multi-cloud setups? That's right, Amazon, Microsoft, and Google, who will be getting paid for hosting everyone else's multi-cloud setups while they get to run their huge infra on their own cloud without fear. The last thing GAFAM competitors - especially OSS projects - need is even fewer economies of scale.
Stop with the victim-blaming, this blunder is squarely on AWS.
Yeah this is the right take, IMO.
Good on you to those of you who actually do multi-cloud backups.
Even if this was just a loss of their infrastructure, it would be catastrophic to any company without good infrastructure as code practices.
Not to mention the downtime.
This sure as shit doesn’t look “customer obsessed”.
Lol "victim blaming" used in the context of a situation with no victims is crazy. The author signed a contract that allowed this outcome and is SHOCKED it happened to them. You and their naive asses can enjoy blaming everyone but yourself.
Did you even read the article? Even under the VERY GENEROUS interpretation of contract law that contracts can't be predatory (which is not a particularly popular philosophical stance outside of cyberpunk fiction), AWS MENA fell short of even their typical termination procedures because they accidentally nuked it while doing a dry-run.
I don't know where you work but if we did that to a paying customer, even IF there was a technicality through which we could deny responsibility, we would be trying to make it right.