Even if the alternate cloud provider goes offline for an entire day it still would be worth it financially compared to AWS because egress is so expensive there.
And for you to just say “it’s okay to be down an entire day” because of egress cost tells me that you have never done infrastructure requirements analysis at scale.
First you have to assess the cost of being down for a period of time, then you have to access RTO, RPO requirements and not all workloads have high egress costs - especially things like data lakes that may have a lot of ingress and processing costs, but relatively low egress costs.
I’ve done a lot of different cloud projects over the years from lift and shifts, to data lakes, to cloud call centers, to serverless, to ETL jobs, you can’t just blindly repeat “egress costs” in a vacuum without understanding use cases.
> Egress price makes it worth migrating away from those three.
> Even if the alternate cloud provider goes offline for an entire day it still would be worth it financially compared to AWS because egress is so expensive there.
You never qualified either with “in my particular use case”. If you had, I would have had no argument. I haven’t been flown into your company along with SAs, sales, project managers, etc for a week to do a proper “as-is” assessment and to see what your requirements are.
I haven’t accessed the competencies of your staff or determined what is your competitive advantage and what is the “undifferentiated heavy lifting” in your company.
I would never make any blanket statements without knowing your specific use case and automatically assume “cloud” is always the right or wrong answer
This suggests you are looking for a single example where the pricing of the big 3 is compratively high compared to the competition at a point where it worth it to switch. I gave the example that the price of egress is one cost which is not competitive. If I had instead said that SQS was not competitive obviously that wouldn't matter to businesses that don't use it enough to make a difference.
Microsoft and AWS have versions of the “Cloud Adoption Framework”
https://learn.microsoft.com/en-us/azure/cloud-adoption-frame...
https://aws.amazon.com/cloud-adoption-framework/
And the TOGAF framework has something similar
https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap...
I am saying when considering any “large” implementation there are a lot of considerations outside of infrastructure bills.
I’m not saying that every company should go cloud. But the “lenses” you have to look through are multifaceted
The bosses would’ve blamed me for choosing a tier 2/3 noname provider the first time a day of downtime happens. And they would’ve been right.