It's not that Microsoft is stealing customers from Amazon. It's that both companies are brining in lots of new to the cloud customers, and Microsoft is just doing it faster.
But both businesses are growing at enviable rates.
It's not that Microsoft is stealing customers from Amazon. It's that both companies are brining in lots of new to the cloud customers, and Microsoft is just doing it faster.
But both businesses are growing at enviable rates.
Besides I’m sure that AWS and Azure are some where in the right top corner of Gartner’s magic quadrant.
The problem is Google can’t make up the market share from only pressuring “lackey” companies that it has leverage over to use their cloud, it has to have a big scale draw for otherwise unaffiliated customers, and to a lesser extent can’t sustain these initial volume & bundling discounts indefinitely.
http://www.cloudcomputing-news.net/news/2018/may/30/office-3...
Also being the discount cloud provider is not an enviable position.
I think Google has done a huge push into education, that alone could reap significant gains in 18 months.
AWS SDKs, documentation and support for Windows/.Net Framework is excellent.
I’m not making any technical arguments against Azure. I haven’t used it besides what is now “Azure Devops”.
As far as Kubernetes. It’s inconsequential when a major corporation is considering which cloud provider to use. Most existing workloads on prem are not using k8s. That goes back to knowing how to meet the customers where they are and knowing how to do a “lift and shift” as phase 1.
https://medium.com/@cfatechblog/bare-metal-k8s-clustering-at...
Edit: Way past the getting-on-board stage, apparently. It had slipped my mind that the article I linked is from 18 months ago and already described an extensive rollout.
MS has decades of building relationships with large companies that it can leverage.
If Google’s only proposition is that it’s cheaper, any AWS Solution Architect can negotiate lower prices from AWS if they want to secure a client that’s large enough.
Also GCP already does have some large enterprise clients. Some of them have had a symbiotic relationship with them, working closely to create the features they need as they scale. That kind of treatment is hard to get with AWS where most enterprises would be small fry by comparison.
There are also enterprises that don’t want to be on Amazons stuff for reasons.
All you have to do is watch the thousand plus reinvent videos to know that AWS does work with many major companies. They also have an extensive partner network.
Microsoft is breaking apart what WAS Windows Server, into discrete managed services. Identity Services, File Services, etc. If you have a need for what was formerly Windows Server provided stuff, and youre rebuilding infrastructure, you would get a lot of compatibility from Azure. Then, as you need other compute and storage resources, youre building on top of a service contract you already have, instead of spreading your data all over the clouds.
Few people get to be CTO without knowing the politics and perceptions involved with dealing with corporate America.
That could be a case for startups but it is certainly not the case for established companies.
The job of a CTO of an established company is not piloting a formula 1 car. Rather, it is to prevent reckless technical decisions from taking an ocean liner and smashing it into an iceberg.
You also need to take into account the cost of changing and tuning your code to run on a TPU.
Oh and amazingly enough, I took the exact same Python file that I built on GPU on my workstation, ran it in Google Collab with a TPU connected, and I really only had to change the configuration to make it work. There was no need to change or tune anything. I was pleasantly surprised by how well that worked.
And let me rant a bit longer, when we started this project I actually first tried to use AWS because our company already had billing set up with them. But AWS was using CUDA 10.0 for SageMaker, which has a known crash- and nan-inducing bug for 2D convolution. AWS support being non-existent as always, we couldn't make things work on AWS and then went bare metal for our GPU training with hetzner.com - which simultaneously also shaved like $30,000 monthly off our bill. AWS's EC2 GPU instances are really expensive when compared to a dedicated root server.
MS recognized moving enterprises with boring workloads to Azure was where the money was along with hybrid computing. That’s how it was able to succeed so quickly.
Besides,Microsoft has always been focused on the dark matter developers doing boring stuff. Their tooling is far better than Google’s and their IDEs that developers are already using integrate with their cloud offerings.
Also, if the only advantage that GCP has is price, that’s not defensible. It’s not like it takes a great engineering effort to change a price.
The market leader can usually afford to be a “fast follower”. That was MS’s playbook for decades.
I posted a link earlier from a podcast interview of someone who works at GCP. She said that only a few small internal projects at Google run on GCP.
This was critical because by then if you weren’t on AWS, you probably didn’t have the DevOps team to do so - MS was now willing to lend you enough consultants to do it for you.
The number of spend shouldn’t be astronomically high. Most workflows in cloud computing are commoditized low-margin. It also explains why Google wants to do high-margin AI stuff, and why AWS is happy with low-margin areas.
Microsoft would say:
“If you have a workload that still requires Windows 2000 and SQL Server 2003. We will help you migrate it to Azure as is and we will extend your support contract.”
While Google will talk about migrating your entire workload to K8s.
Part of Microsoft's implied message in heavily marketing K8s is that they know GCP is heavily K8s-based, and know GCP is heavily competing with them on price, and they are counting on some of that "dark matter conversion work" wanting to move towards the "more portable solution" in order to "maybe when the moons are right eventually shift over to GCP or something cheaper than Azure". By offering that conversion path at all, and knowing Enterprise's weakness for sunk costs development over from-scratch rewrites, they are playing a very different game than what GCP can offer.
Even if you did everything in a “cloud agnostic” way, once you have even a couple of dozen VMs, your networking infrastructure and security rules, your user permissions, your DNS entries, your site to site VPNs, your client to site VPNs, all your data in databases, security and compliance audits etc. migrating your infrastructure is going to be a months long process, involving project plans, regression tests, and still have little to show for it.
I was involved in a much smaller migration as a dev lead when all we had to do was migrate to WorkDay for HR, payroll, and time tracking. That involved tons of integration work and hiring Workday consultants. Not to mention consolidating all of the other SAAS solutions that we had to integrate when we merged with another company.
It's why Azure's K8s strategy is so fascinating: precisely because the more they make it "cloud agnostic" on paper and are good K8s/Docker citizens the greater power they have for Manager mentality lock-in to the non-cloud agnostic stuff (especially "lift and shift").
Also, a huge amount of cloud costs are based on egress, so having it on one cloud saves you resources.
All the major cloud storage providers tout geo-replication so that if an earthquake or meteor takes out a datacenter there’s still other copies.
But nothing can protect against an administrative SNAFU where you - or your cloud provider - and accidentally or intentionally deletes your account and everything’s gone in an instant (yes, there’s usually recourse and backups to recover from - but that’s hours or days of downtime).
Sometimes it isn’t even the cloud provider’s fault: see Adobe’s blameshifting onto the US executive for their dropping all their Venezuelan customers.
While Azure has the “Black Forest” unit which is legally - and technologically - firewalled off the main Azure cloud - and you can also license Azure Stack for running many (most?) of Azure’s platform on-prem or self-hosted, I haven’t seen similar offerings from AWS or Google.
To your point though, yes there is business risk of having it on one cloud.
The trick is to buy both MSFT and AMZN, and relax!