Maybe its because I'm a .Net dev but everythings been working out pretty good for me on Azure. Half the stuff I do on a daily basis I can do from VS to begin with. About the only problem I've run into is having the azure instance override certain configuration settings I had in my app when I published it, but I haven't run into that issue in a while.
Networking - first, when they had the idiotic "Classic" design where you had to share an IP for no reason. Then sometimes, the network just wouldn't work very well. We'd get Pingdom alerts even though the site was up and responding. PCAP showed TCP issues. Same issue with Azure CDN, until we re-created the account and selected Akamai. Or Verizon. It's just silly.
VMs hanging, and the suggestion being to stop/start or resize them to get them unstuck.
The moronic SSD situation. Seriously, you need a special class of VM? And for a while, that meant you got an "erased-at-any-time" temp drive SSD. Can't choose size of SSD, must use one of 3 presets. And if you need more perf/storage, they suggest RAIDing them together. It's a joke.
Everything slow and overpriced. GCP is 20-80% less than Azure for VMs - even getting an enterprise agreement didn't help much. And that's not even getting into scheduling preemptive VMs on Google.
SQL Azure seemed really slow (so we had to pay for the premium level) and prone to connection resets or "transient errors" requiring special coding. This was not using anything exotic or heavy workloads, we just got shit IO out of it, even at the, I think, $400/mo tier.
Everything just being "clunky". Networking rules, for instance, are just straightforward on GCP. Ping works, unlike on Azure (wtf guys). And again, I cannot stress how much of a pain that portal is. Maybe I should have everything scripted, but hey, I don't. It's just confusing, and even when you know where things are, it just feels cumbersome and slow. Perhaps I shouldn't be using subjective adjectives, but hey, there it is. And I know I'm not alone.
I get it. Azure wanted to be a full PaaS where you just uploaded your .NET dll and la-di-da. Unfortunately, a: Windows is terribly suited to not having RDP, and b: sometimes we just want IaaS. I also get that they're going to make bucketloads of money getting their enterprise customers cloudified. Existing AD/Exchange deployments aren't just gonna jump over to Google, but they'll migrate bit by bit to Azure and pay nicely for it.
I agree on the issue about the portal. I think they are trying to bring everything Microsoft into cloud which is really a pain.
> I also get that they're going to make bucketloads of money getting their enterprise customers cloudified. Existing AD/Exchange deployments aren't just gonna jump over to Google, but they'll migrate bit by bit to Azure and pay nicely for it.
I am wondering whether enterprises would go for GCP or other IaaS/PaaS for that matter if Exchange is something that can be replicated by Google.
I used to work a company that uses everything Microsoft but really other than Office, I do not think I will miss anything if the company suddenly decides to choose other vendors.
What is the situation in US/Europe that most enterprises hold so tight to Exchange?
