As usually Corey makes a lot of great points in his post but I don’t agree completely with his assessment.
From an account level, yes Azure is easier to get rolling with and if they do any level of integration with GitHub, it’ll be a huge game changer.
But I like to look at this one more along the lines of how people build. Here I think Google Cloud is actually the sweet spot but the business of Google Cloud prevents it’s adoption.
Google has just the right amount of services in the right categories. Builders don’t typically get lost trying to figure the difference between service A1, A2, and A3 where that’s happening more and more with AWS.
The APIs and data structures on Google also align a bit more seamlessly with how builders are thinking. They’re not perfect but there’s a lot to love there from a technical perspective.
You’ve already pointed out “Killed By Google” and that’s part of the story. The other part is that it’s a very opinionated cloud and the service & support teams around it often align to that opinion. So if you’re going things the “Google way” you’re golden, if not, it’s really hard to build a business on top of that cloud.
So yeah for the tech, boo for the business.
AWS continues to crush it because the most effective way to use AWS is to ignore 80% of it. There’s simply too much there at this point but if you can focus (and find) the few services that meet your needs, you’re all set.
Azure is extremely “Microsoft-y”. They are getting a lot better at shaking that but some of it is built into the core of the cloud. So while Microsoft builds great developer tools (VSCode and others), the building blocks range from meh to amazing.
At this point, none of the cloud is a slam dunk which is why a lot of teams keep building on AWS. They have such a massive lead, that it’s become the default choice.
What I’m really buoyed by is that teams are finally starting to look beyond just the tech into things like pace of innovation, cost, support, and community!