We use RabbitMQ hosted on Azure via CloudAMQP. We had almost half a day of downtime because Azure performed maintenance on our instance, involving a restart.
CloudAMQP told us that Azure do this without notifying them, or us! We got told by them if we moved to AWS rather than Azure this wouldn't happen. AWS notifies you two weeks in advance and can allow live migrations without any downtime.
They said they don't actually recommend hosting on Azure!
> Azure functions is inferior to lambda/cloud functions.
I don't know for the other ones but the tooling for lambda is definitely better on aws, I had to patch around 500 lines of serverless-azure-functions to allow for missing features & fixing bugs. I should probably do a cleanup & do some pull requests one day.
Azure's woes are well documented. I've experienced them first hand. In fact you'll find me with ~hundred upvotes describing my experience with Cosmos in one of these threads. Most engineers will take take aws/gcp without GUI tooling any day over Azure and its sea of undocumented bugs, performance issues, unlogged failures, and blown SLAs.
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.
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.
As an rdms? In what way? I mean, I do personally prefer Free software - and while it's possible, I think it'd be a bit premature to run ms sql in production on Linux - but "inferior" seems a bit harsh?
At what scale? For what kind of workloads? Use cases?
CosmosDB is inferior to postgres or cassandra depending on use case.
Azure functions is inferior to lambda/cloud functions.
Azure in general is vastly inferior to aws/gcp. That's a point which is reiterated on a monthly basis on HN.
None of these three points are opinion. They're well covered facts.