>However, everyone that I've heard of that understands cloud native type architectures that has attempted to deploy into Azure is looking to leave.
Extremely unsurprising, but I'd be interested to read more.
Extremely unsurprising, but I'd be interested to read more.
However, that correlates pretty closely with my own personal experience. I've worked with a fair bit of the Azure products and it feels to me very much like a work in progress.
The identity management stuff has been a moving target since day one. That is, how to authorize against the service itself. This is apparent in many of the Python libraries where this is documented.
The Python libraries that I've seen look like they were produced by interns. I'm performance with ADL is pretty rough.
My main goal with Azure was to deploy Kubernetes clusters there. The list of problems is very long and has been documented ad nauseum in many Medium articles. In the 14 or so months I've been working with Azure, it hasn't improved as quickly as I'm accustomed to with AWS and GCP.
A year ago, I shifted the majority of my production infrastructure from AWS to GCP. By comparison to Azure, I was pleasantly surprised with the quality of the products from GCP. My company uses GSuite which made identity management and RBAC a breeze. The GKE product is way, way better than anything else, and there are a handful of things that I like better than AWS.
I wouldn't encourage anyone to shift from AWS unless they were planning a large Kubernetes implementation. I would encourage folks to try GCP and especially GKE to get a sense of the differences.
There's nothing about Azure that I've discovered yet that would cause me to recommend it to anyone. It's possible that if a company had a heavier investment in MS products that it might be worthwhile, but that's not the case for mine. We only ever use MSSQL occasionally for development purposes and I've found that I can spin up an instance of that quite nicely in k8s with the Microsoft authored helm chart.