91–100 of 223 posts
The 'experts' also made similar criticisms with the Fastly outage in 2021 and did anything obvious change as a result? In a week's time no national newspapers will be talking about this. Meanwhile, everyone that spends actual time in these areas: - Knows that running an operation at AWS scale is difficult and any armchair critism from 'experts' is exactly that. Actions speak louder than words. - Understands that the…
I sincerely hope that the base functionality of these doorbells (i.e., triggering the ringing of the bell within the home) is preserved in the event of an internet outage.
Been a while since I worked in cloud but at least when I got out of it, the primitives where all shoring up to be generally very similar. Did multi cloud redundancy end up being too expensive? Tech didn't line up enough? No good business case? The elastic cloud story that never was? https://www.slideshare.net/slideshow/pets-vs-cattle-the-elas... What happened?
If you're a company providing services to people that already have data stored in VendorA's cloud, being on a different cloud would be expensive and prevent you from winning much work. If it turns out that VendorA happens to be the vendor for your clients, you build your services to run on VendorA's cloud too. This is the situation for my company that started with the intent of being platform agnostic, but it quickly…
Because it rarely is. Occasional downtime is just a cost of doing business. It is, or should be, rare enough that you just take it as it comes instead of trying to have a redundancy. We don't build tunnels everywhere as a backup for surface roads on snowy days. We just cancel school and work for the day and make up for it later. Do some important things get impacted? Sure, but most things are as mission critical as we make them out to be. The press coverage of an AWS outage makes it so easy to shrug it off and point fingers.
Earlier quoted context omitted.
Same thing applies to AWS...
I’m not really making a point here as much as an observation, but if my stack that I manage atop VMs in a data center goes down, my customers are pissed at me. If AWS goes down along with half the Internet, my customers are completely sympathetic.
Man, I did not have "AWS us-east-1 will only have TWO 9s this year" on my bingo card.
For those of us who have been using AWS for almost 20 years now, I can't imagine why anyone would willingly choose us-east-1 for anything. It is the oldest, highest traffic, most critical path region and is subject to turbulence.
Earlier quoted context omitted.
exactly what tools helps make your large volume of data stored in a down region available to other regions without duplicating the monthly storage fees?
You duplicate the fees. But it's the same or worse trying to do multi cloud.
Man, I did not have "AWS us-east-1 will only have TWO 9s this year" on my bingo card.
For those of us who have been using AWS for almost 20 years now, I can't imagine why anyone would willingly choose us-east-1 for anything. It is the oldest, highest traffic, most critical path region and is subject to turbulence.
Earlier quoted context omitted.
All the cloud providers have cheap compute but ludicrously expensive network egress. Trying to multicloud will stick you with a massive traffic bill, which is probably not a coincidence.
It's a market regulation failure. Which results in a failed market, with the cloud infra provider also providing data services. 20 years ago, there were 20+ widely used operational databases. Now, it's like DynamoDB with like half the market.
Should we similarly cap say Front End frameworks on market penetration / growth? Is react too big to fail? Do we need to force some of it's users to use something else?
Earlier quoted context omitted.
You duplicate the fees. But it's the same or worse trying to do multi cloud.
Which is precisely why it's not done