Hmmm. The link you gave was the wrong zdnet link. It's this:
https://www.zdnet.com/home-and-office/networking/one-aws-failure-took-down-the-internet-monday-morning-what-went-wrong/
It's more than just a database problem, yet a DNS cloud server problem.
Sort of a different animal all together. To my knowledge there really isn't a good cloud based database anyway. Hense the need to create their own database. Proprietary was the only way to go.
It sounds like you're referring to a significant issue with DNS servers impacting internet services, which highlights the complexities and vulnerabilities in cloud infrastructure. You're right that DNS failures can cascade into broader internet outages, affecting many services simultaneously.
Understanding the Issue
DNS and Its Role
DNS (Domain Name System) is crucial for resolving human-readable domain names into IP addresses. When a DNS service fails, it can cause widespread issues, as many users and services rely on it to navigate the web.
Impact of AWS Outages
The AWS failure you mentioned likely triggered ripple effects throughout various platforms that depend on AWS services, including database solutions. When core services fail, it can lead to significant outages and disruptions in connectivity.
Proprietary Databases
Your point about proprietary databases is well-taken; many organizations opt to build custom solutions rather than rely solely on existing cloud-database services. This can provide more control, tailored performance, and enhanced security.
Current Landscape
The reliance on cloud services often brings up debates about resilience versus convenience. While cloud databases can scale rapidly and are managed by service providers, they do come with potential risks, such as outages, as you've noted.
