The Growing Case for a Microsoft Azure Slowdown [pdf]
dadavidson.bluematrix.com
dadavidson.bluematrix.com
The whole thing is full of weird terms and workflows. For example, I tried setting up a simple static site with CDN and abandoned frustrated after a couple of retries.
IMO Google has the best cloud dashboard of the three big ones. You don't need to read a book or take a course to understand what's going on.
Maybe there are more greenfield and small devs. going to Azure, and more mature/ported solutions that just scale in containers and need raw CPU/network on AWS/GCP?
What part did you get stuck on?
I was making a benchmark of static hosts and wanted to include Azure but simply desisted. I had no problem setting it up on any other provider.
They are reasonably consistent with their nomenclature and their error messages, but I definetely felt I was using a jackhammer to put screws in drywall. The amount of settings and types of setups per product is staggering. You definetly need to read a how-to to figure out what to do. You cannot figure it out on your own.
In terms of UI, the fact that every separate product uses a different view model is bonkers. I understand that letting each product reflect its own functionnality is important, but a list of checkboxes should not have three different ways to display them across three different products (Route 53, S3, CloudFront). Oh and those naming schemes, jeez. Who thought Route 53 was a good idea?
That's a great metaphor to describe this. :)
at the start of quarantine, the azure console was just dying on me regularly. we couldn't get the instances we needed, and apparently neither could the service running the console.
They definitely know about it — every time I've used it with someone from Google in the room they've apologized — but it's one of those things which I think their management doesn't prioritize because they either don't use it much or only do so over very fast network connections.
I can't stand the GCP console... especially the networking UI's
I'll take either AWS or Azure's console any day... though really I spend most of my life trying to avoid the console and just automating somehow.
Tom Forte, CFA (Managing Director, Senior Research Analyst), and/or members of his/her household, holds a long position in securities of Amazon.com, Inc.
That's only true if you include ETFs/mutual funds/pensions, but I don't think you need to make a disclosure in those cases.
in this case owning some S&P500 ETF in significant quantity would be to his credit: MSFT would be 6% of holdings, to AMZN's 4.49%.
> Amazon is already building an ecosystem around its own chips, while Microsoft has yet to deploy any custom chips in Azure.
They do have Intel Arria (Altera) FPGAs:
https://docs.microsoft.com/en-us/azure/machine-learning/how-...
Edit: And some evidence that it's a custom setup: https://www.microsoft.com/en-us/research/uploads/prod/2018/0...
> Tom Forte, CFA (Managing Director, Senior Research Analyst), and/or members of his/her household, holds a long position in securities of Amazon.com, Inc.
I think a lot of Azure fast growth was migrating existing corporate IT workloads. These are Windows servers, SQL Server databases, etc and Azure is a great place for those.
But if you are building a new app, I am not quite sure why you would choose Azure unless you are afraid of Amazon.
How is running a search through a free government database/website proprietary?
I also can't find a single mention of Office which is a "cloud" monster itself.