5
A single point of failure triggered the Amazon outage affecting millions
(arstechnica.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Oct 2025
5 points (100.0% liked)
Technology
83666 readers
1101 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
We don't have to. It is entirely possible to engineer applications and services in a way that they're not dependent on any one cloud service, while also using cloud services for IaaS. Netflix famously does this, and sure enough Netflix experience no service interruptions during this latest outage despite having a large AWS presence.
If we want a truly robust system, yeah, we kinda do. This sort of event is only one of the issues with allowing a single entity to control pretty much everything.
There are plenty of potential issues from a corrupt rogue corporation hijacking everything to attacks to internal fuck-ups like we just experienced. Sure, they can design a better cloud, but at the end of the day, it's still their cloud. The Internet needs to be less centralized, not more (and I don't just mean that purely in terms of infrastructure, though that is included of course).
What I'm advocating for is the opposite of "allowing one entity to control everything".
https://en.wikipedia.org/wiki/Chaos_engineering#Chaos_Monkey
Read about it dude. Netflix has a large presence in all major cloud providers (and they have their own data centers), but has a service whose uptime is NOT dependent on any one of those hosting environments. The proof is the pudding - Netflix service did not go down in the recent AWS outage, nor in the last one.
All of that can be achieved WITHOUT completely abandoning public cloud services and having to completely host all of the hardware for their services.
Yes, Netflix had their own infrastucture in addition to other multiple redundant cloud services for their CDNs: You're kind of proving (part of) my point?
How? Their reliability would exist without that. There's nothing inherent to their own data center that makes their setup that much better. Having a distributed system across multiple cloud service providers means your actual chance of downtime (here I mean inverse of uptime) is their individual chances of uptime multiplied by each other. In other words, they all have to go down for your service to fail. The catch is you have to use only commodity IaaS and PaaS, nothing proprietary to one CSP.
For smaller companies especially, in terms of pure reliability, there's no reason to think that they would be better at running a high availability data center than Microsoft or AWS or Google.
Parallel distributed architectures give you the advantages of using public cloud (not having to physically manage your own data center) without the disadvantages (dependence on any one cloud vendor), while also potentially increasing your reliability beyond the reliability of any one of your cloud vendors . That is why Netflix is so rock solid.