Comment on Load bearing Tupperware
undefined@lemmy.hogru.ch 22 hours agoOnce per year? I had outages much more often than that on AWS.
Comment on Load bearing Tupperware
undefined@lemmy.hogru.ch 22 hours agoOnce per year? I had outages much more often than that on AWS.
CallMeAnAI@lemmy.world 21 hours ago
Nah. I haven’t had a service we use miss an SLA or cost more than it’s SLO budget in 2 years.
What specific services have they missed your SLA on and what incidents were they tied to? I understand that not every team has a guy on their team to monitor that that stuff and bitch for credits, but I do, and AWS is one of our most reliable vendors.
Look the fact that AWS, Azure, and more recently Google are the only choices sucks.
But the reality is most companies and projects don’t have the business case to justify multi region fail over much less vendor fail over. They are all built on single points of failures and will always have outages.
Everyone just notices it more when it’s AWS. And that’s a stupid reason to base decisions off of. Visa/mc was working. Reddit and Facebook were mostly working once they started routing through their multi cloud nodes. Maybe you couldn’t get to your banks web app, that’s on them using a single cloud with no way to route to alternate cloud nodes and services. And for them to double at best infrastructure costs, unless they are boa Chase Morgan etc, is dumb for 99.99% which is the SLA .
The world isn’t ending, emergency services are working, visa/mc failed over, I was still on Reddit and slack most of the day. It wasn’t the end of the world.
Anyway, I now realize I have summoned my frustrations with this entire thread and gone wildly off topic and ranted with full force at you.
I just don’t think it’s important that when there is a major outage on AWS/Azure/cloud flare. It was going to happen elsewhere, and you wouldn’t have an excuse to tell your pm not my problem, instead of digging into your app for 2 hours to find out x portion of you very distributed vendor list failed and you still have a single point of failure. I’d rather be able to point to AWS, say shit is fucked for everyone, and if you want multi cloud it’s going to cost at least 1.5x as much as we’re spending 🤷♂️.
undefined@lemmy.hogru.ch 17 hours ago
I haven’t used AWS in years. No IPv6 support in S3 in 2017 was the last straw for me. I have to deal with it at work (sometimes) and always laugh when they introduce “new” features like HTTPS records in Route53 like two years late.