Needy Child Rule
Fuck the centralized cloud why does my job require it
Also "everything is so reliable in the cloud everything is better in the cloud" my ass, not even the Microshit status page shows any error, but just look at downdetector and it becomes obvious
18 replies
The best way to avoid a single point of failure is to create multiple parallel single points of failure, right?
Just use all the hosts, and then implement a distributed RAID-esque system to mirror the information across all those various cloud services...
that is legit what a bunch of multicloud vendors claim to offer. the REAL problem is all three major cloud vendors have a single choke point that is a coal fired coal plant in Charles Town, West Virginia that provides 60% of the electricity provided by Dominion Energy to Nothern Virginia
That coal plant, to avoid 'woke' environmental retrofits, has had exactly zero maintenance since 1997 to keep grandfather clauses running.
remember that when amazon says US-East-1 is carbon neutral. it's all carbon credits. and look. carbon credits have their place. but when the world's largest business is reliant on them to make outlandish claims to fuel unsustainable infininite growth, all that's happening is innovational stagnation.
I'm honestly of the opinion that the credits create more harm than good, because it lets companies pay their way out of being green. So the bigger you are, the more you can find a scheme that may or may not actually sequester that amount of carbon (and definitely not at the rate of production).
at this point, the absolutely do. as a society we have outgrown them
Used to be grandfather claus didn’t start running until December smdh.
What happens if that power plant is down for 24h?
Kubernetes just called, they're asking why you only deployed nodes on AWS.
I'll confess that I'm only passingly familiar with kubernetes, does it allow for this?
Kubernetes doesn't care how many servers and from what cloud provider you use, if you add 20 AWS, 20 Azure and 20 google cloud servers and set up a master (or more) on each provider with the rest being workers, then your servers are completely replaceable as long as the rest can take the load.
The only complication is the client connections. You'd have to split your external ips across all three providers and across countries/Geo regions.
Worse case then is that you lose AWS/Google/Azure and with it the regions that used the AWS/Google/Azure ips, then you'd have to failover DNS to the remaining IPs.
In short: It's possible and the main problem is the user being able to connect after fail over after the original IPS change.
Some goobers definitely using AWS compute with Azure AD for identity and got hit by both.
Sadly, pretty much everyone in the corporate world uses azure to some degree.
Yeah I know :*(
someone at our place has their tongue perpetually shoved deep into someone from microsoft's ass. We're a small country of half a million people. Most of our things do not need to hyperscale. But everything is getting moved to the cloud. Did I mention that we have our own datacenter? The national one. Yeah...
Cloudflare did this too. Bad month ig