Sadly, there are some who don’t even know it, because they’re buying services from someone else that buys them from someone else that buys them from Amazon. So they’re currently wondering what the fuck is even going on, since they thought they weren’t using AWS.
That’s not really fair, I think. Smaller organizations are especially dispositioned here. Think small businesses, charities, local municipal services, etc. Small IT budgets, low staff (if any) and just enough to pad out a subscription cost to a service provider that fits their needs.
AWS is an incredibly low cost solution, and it’s probably where most of these low cost services point themselves at when building platforms at scale. Not everyone can build and maintain a datacentre or home server for their every need.
This isn’t to say that there are definitely idiots who pad their resume by chanting a prayer to SaaS and boasting about having moved their company to the “cloud” via a cheap and unreliable AWS rehoster, before failing upwards though.
Sure, but online services can certainly leverage multiple modules, from multiple companies, hosted in multiple places. So maybe your site mostly works fine, but a key aspect of it is broken.
Yes, it’s much more expensive to have two providers. Both in terms of outright costs but even more so in terms of ongoing engineering/technical overhead.
The calculus is how much the expectation downtime is, versus that cost. It’s a reasonable calculation and TBH if outages are a few hours once every few years for most cases it’s acceptable.
OFC if your hospitals or emergency services depend on a cloud service, you happily fork over the extra money same as you do for any other insurance.
Walmart.com would likely work fine, as they are rabidly anti-Amazon, especially AWS. They don’t even want their SaaS vendors using AWS under the covers for them.
Can confirm, about 10 years ago, the company I worked for migrated to AWS, and I managed the transition. We planned everything meticulously so that there would be no downtime, and used it as excuse to fix a lot of tech debt. No one was supposed to even notice the cutover, and when we did it, I expected the only feedback to be that things seemed faster and were working as expected. A few hours later, we get a complaint from an Account Manager for Walmart that they can’t access the platform at all. There was a lot of confusion and back and forth, turns out their IT department had an allow list or something in the corporate DNS to not resolve to AWS owned IPs unless approved. We eventually got them to add our domain to their allowlist, but it seemed insane that they would spend the effort to implement and maintain that level of control.
You’d be hard pressed to find an online service that isn’t associated with AWS in some way.
Sadly, there are some who don’t even know it, because they’re buying services from someone else that buys them from someone else that buys them from Amazon. So they’re currently wondering what the fuck is even going on, since they thought they weren’t using AWS.
Well those people are fucking idiots.
That’s not really fair, I think. Smaller organizations are especially dispositioned here. Think small businesses, charities, local municipal services, etc. Small IT budgets, low staff (if any) and just enough to pad out a subscription cost to a service provider that fits their needs.
AWS is an incredibly low cost solution, and it’s probably where most of these low cost services point themselves at when building platforms at scale. Not everyone can build and maintain a datacentre or home server for their every need.
This isn’t to say that there are definitely idiots who pad their resume by chanting a prayer to SaaS and boasting about having moved their company to the “cloud” via a cheap and unreliable AWS rehoster, before failing upwards though.
Fine, most of them are fucking idiots. Know where your infrastructure is people! Whois your IP.
I’m pretty sure most of Azure (Microsoft), OCI (Oracle), and GCP (Google) have all been fine.
Bezos is a craven beast but I don’t see many companies above with CEOs that I’d feel comfortable babysitting my teenage daughter
The company I work for is an Azure shop. However, our provider for customer 2fa tokens uses AWS… So still in trouble.
Once Larry Ellison owns TikTok he’s going to be babysitting all the teenagers and a whole bunch of other people!
I really hope that super villain wannabe croaks out real soon
I don’t think his son is any better.
If daddy croaks now we will see how much is actually David’s doing vs Larry
Sure, but online services can certainly leverage multiple modules, from multiple companies, hosted in multiple places. So maybe your site mostly works fine, but a key aspect of it is broken.
See the above post from the Azure shop … that uses AWS for 2FA tokens
You want to add multiple companies in parallel as alternates/failovers, not in serial where any one failure blocks the whole flow
Also allow things fail gracefully, independent of each other.
But that would cost more money, that’s anticapitalist.
Yes, it’s much more expensive to have two providers. Both in terms of outright costs but even more so in terms of ongoing engineering/technical overhead.
The calculus is how much the expectation downtime is, versus that cost. It’s a reasonable calculation and TBH if outages are a few hours once every few years for most cases it’s acceptable.
OFC if your hospitals or emergency services depend on a cloud service, you happily fork over the extra money same as you do for any other insurance.
If there’s anything I know, it’s that “businesspeople” are never proactive.
Lemmy seemed fine, Reddit did not.
Federated, open source
Centralized, corporate
Amen to that, good thing though. Got me to learn what Lemmy was. Apparently I’ve been under a rock.
Welcome to the fediverse!!
Walmart.com would likely work fine, as they are rabidly anti-Amazon, especially AWS. They don’t even want their SaaS vendors using AWS under the covers for them.
Can confirm, about 10 years ago, the company I worked for migrated to AWS, and I managed the transition. We planned everything meticulously so that there would be no downtime, and used it as excuse to fix a lot of tech debt. No one was supposed to even notice the cutover, and when we did it, I expected the only feedback to be that things seemed faster and were working as expected. A few hours later, we get a complaint from an Account Manager for Walmart that they can’t access the platform at all. There was a lot of confusion and back and forth, turns out their IT department had an allow list or something in the corporate DNS to not resolve to AWS owned IPs unless approved. We eventually got them to add our domain to their allowlist, but it seemed insane that they would spend the effort to implement and maintain that level of control.