Comment by jiggawatts
16 hours ago
This is certainly... an opinion.
AWS's us-east-1 famously takes down either a bunch of companies with it, or causes global outages on the regular.
AWS has a terrible, terrible user interface partly because it is partitioned by service and region on purpose to decrease the "blast radius" of a failure, which is a design decision made totally pointless by having a bunch of their most critical services in one region, which also happens to be their most flaky.
Nobody is winning any UX prize there. Azure, AWS, GCP... they are all terrible. Back then GCP for instance used to only work reliably on chromo-based browsers. Azure has that horrible overlay UI that abuses extended real estate that just doesn't work.
But azure wins most prizes for being terrible becuase, among other things, https://isolveproblems.substack.com/p/how-microsoft-vaporize.... It's not the worst provider maybe because oracle is somehow still kicking around.
Its just a bad product. Just like windows, OneDrive, teams and basically everything Microsoft has pumped out in the past decade.
Microsoft is in the top 5 most valuable companies in the world. It's got azure that is a huge cloud provider. And yet it was utterly unable to present its answer in the AI race. Not even a bad model with a half baked harness. Nothing. And meanwhile they are trying to port NTFS to low powered FPGAs because insanity. Just let that sink in.
Check out hetzner ui (regardless if you like their services, i know some ppl have opions or experiences lol) BUT, their cloud ux/ui is fantasties for a cloud company!
I worked extensively with Hetzner and I love them! But it think they are in a different class than these other providers, mainly in terms of global presence so I didn't include them and wouldn't for instance recommend them to my current employer. But indeed the Hetzner console is great. The robot not so much, but it's serviceable.
I don’t see how you could care (a lot) about both the UI and reliability.
One is caused by the other. Amazons engineers decided to split the interface in a “user hostile” manner with the stated purpose of increasing reliability… which didn’t materialise. The clunky UI did.
Or maybe you can provide a better explanation for why users had to “hunt” through hundreds(!) of product-region combinations to find that last lingering service they were getting billed $0.01 a month for?
This just doesn’t happen in GCP or Azure. You get a single pane of glass.
One of the things I find about AWS is that every service UI feels different. It's like every service was designed by a totally different team.
For all its flaws at least Azure has consistent UI.
4 replies →
I mean, if you care about the reliability of your own service you would not be using the AWS UI at all. Use the api, via automation.