If we are playing anecdotes, I also had an horrible experience with DynamoDB last year, maybe I should write a blog post about it as well.

Or some other ones about the automated replies and lack of human support on GCP.

> The only reason to use Azure today is either because it's the only thing you know or because there are external forces making you do it.

Sure, that is why GCP is playing catchup with Azure and Microsoft had such a huge loss in Azure profits during the last years. /s

> If we are playing anecdotes

Anecdotes stop being anecdotes when you're looking at well over a hundred consistently negative experiences from different users across a number of unrelated discussions. At that point those anecdotes become the consensus. Try to find 1/10th of this many HN users shitting on aws or gcp, you won't be able to.

I didn't pick up azure looking for excuses to shit on it, like you appear to be doing and confirming in your profile bio. I came ready to deliver on the next round of projects, expecting something resembling parity with the other cloud vendors. And walked away feeling borderline defrauded by the delta between how MS markets azure and what it actually is.

"Said someone that never used either SQL Server or its GUI tooling."

You just sound like an angry teenager lashing out because their one and only skillset was shown to be poorly chosen. I'm pretty sure I've been using SQL server longer than you've been in the industry. It's middle of the pack at best today, sorry.

Yes your cases are anecdotes. There are plenty of AWS examples to refer to, including some region failures posted here or how one needs a PhD to jungle around their offerings and administration panels.

My profile bio is what I do in 2019, not what I have done since mid-80's.

In fact I have my share of delivering projects in AWS, across multiple kinds of stacks, all the way back when EC2 was started.