Hacker News new | ask | show | jobs
by justinlaster 3477 days ago
It most likely is out of date, but I've continued to see the same sentiments echo'd from other people recently, so haven't bothered to fully revinvestigate. I got the impression from my time with Google's offerings that their culture of "we're consumer focused, not devop focused" (anything from API's to reporting) completely plastered their offerings in the cloud space.

>most also support GCP, but very few support Azure.

This might be a case of different tech stacks, but nearly everything I work with supports Azure. Sorry to ask this, because it might be easier for you to provide an example or two what you specifically know doesn't work with Azure versus me providing everything that does (and of course, these should be semi-popular tools in whatever "stack").

1 comments

> I got the impression from my time with Google's offerings that their culture of "we're consumer focused, not devop focused" (anything from API's to reporting)

Huh? What does "consumer focused" even mean in the cloud space?

Google has made a substantial effort to buff up their cloud offerings in the past few years and it definitely shows. (AWS is still my first choice though.)

> This might be a case of different tech stacks,

That's true. If you're working with a Microsoft stack then of course Azure will come out ahead. I'm coming from a generic Linux background.

>What does "consumer focused" even mean in the cloud space?

Nothing. It's their general company culture. They don't tend to actually create good API's/tooling in my experience. It always seems like an after thought. From google maps to their cloud offerings.

>If you're working with a Microsoft stack then of course Azure will come out ahead. I'm coming from a generic Linux background.

I work with Linux and Microsoft stacks on a daily basis, but certainly that could just mean I've chosen tools that explicitly won't conflict with each other. However, I'm still interested to hear what tools don't work with Azure (with the assumption that there is some quality about Azure that prevents/disincentives that tool from doing so).