Discussion: GCP, AWS and Azure

4 points by pradeeprajr93 ↗ HN
GCP, AWS and Azure are like 3 parallel universe. What is your take on cloud learning curve?

Let's have this as a resourceful conversation. No reactive comments please.

9 comments

[ 3.1 ms ] story [ 34.6 ms ] thread
The three have a lot in common, with key differentiators e.g. the backbone connectivity of GCP is far different than that of AWS.

What worked for me is that I went deep into one of them, then uses this resource to 'map' what I learned on GCP to AWS: https://cloud.google.com/docs/compare/aws (use the table mid way down the article), and this gave me a great framework on which to build my AWS knowledge.

A similar table exists for Azure (https://cloud.google.com/docs/compare/azure)

AWS has replaced IBM in "you're never going to get fired for buying <X>". It commands the overwhelming share of the market, and has a solution for most computing requirements. That being said it has problems too.
I've used both AWS and GCP and I personally found GCP easier to use. Also FWIW GCP ended up being cheaper, at least for running GPU instances.
Aws, azure, gcp by market share. We went GCP, overall it's not moving as fast as the others but they are working on that. The services are extremely stable. If you use the PaaS products by cautious, Google's product management has gaps. Their Api gateway portfolio is a mess. I just heard Dialogflow now has a new product called CX, not backwards compatible and no port options either.
Whats your goals? Are you looking to make a technology decision for a product, or are you looking for one to learn to help you get a job?

If you're looking for a job, AWS has the largest market share (33%), followed by Azure (19%), and GCP (9%).

If you're looking for a place to host your product, you probably can't go wrong with either of the three, but there are some minor considerations...

Personally, I would consider GCP a little more risky long term. There was a report last year about Google considering existing the cloud business and setting a goal to be a top two player by 2023. Since this seems unlikely, what then? Google has some anti-trust concerns, but the bigger anti-trust concern is probably Amazon. There is a non-zero chance that AWS gets split out from Amazon at some point.

Finally, I don't really know GCP that well, but it's my understanding it's a little easier to manage for smaller teams. I believe AWS is considered IAAS while GCP is more PAAS (although the lines get blurred depending on product). In my experience, for companies using AWS... having a DevOps team that smooths over the rough edges of AWS and provides tooling on top of AWS warts has been a requirement.

I have no experience with Azure, but I can't see Google out performing Microsoft in any world as long as MSFT has .NET stack.

I would disagree with the IaaS and PaaS distinction with AWS and GCP. Both have many many different services. They both provide an IaaS (compute instance) service and they both have a PaaS offering, among many others. Azure is in the same boat as well.
> I believe AWS is considered IAAS while GCP is more PAAS

There was a time when AWS had an IaaS and no PaaS and Google has a PaaS but no IaaS, but that's long (in public cloud offerings time) past.

Guys I’m just curious are you supposed to learn Golang when dealing with cloud services
No. Lots of cloud native tools are built with go, but there is absolutely no reason you need to learn it.