Live data from Hacker News

Google Cloud vs. AWS Onboarding Comparison

kevinslin.com

121–130 of 394 posts

Re: Google Cloud vs. AWS Onboarding Comparison

#122

It's not much better if you end up being a GCP customer. My company has gone through 4 reps in 3 years. Every time we get a new GCP rep they just want to talk to us about "expanding our use of GCP offerings". The only thing they want to talk about is starting to use BigQuery - not my business at all. I signed up for a Google Cloud Security summit, and afterwards a sales rep reached out me. It was obvious from the sta…

This has also been my experience.

When we first launched on GCP, there was no question that it was the way to go (frankly, because of BigQuery). Working with AWS, when we launched, was going to cost us significantly more up-front, before we had even brought on our first customer.

Fast forward 5 years... AWS has closed the gap in every way that matters. I still, frankly, trust Google's Security more than Amazon's, but I don't encourage folks to use GCP the way that I used to.

Just the opposite. In 2021, no questions asked, it's either AWS for general compute, or something more targeted if your business doesn't need it.

Until you get to the point where your bill is larger than a dozen engineering salaries, you won't get any respect from these people.

Re: Google Cloud vs. AWS Onboarding Comparison

#123

It's not much better if you end up being a GCP customer. My company has gone through 4 reps in 3 years. Every time we get a new GCP rep they just want to talk to us about "expanding our use of GCP offerings". The only thing they want to talk about is starting to use BigQuery - not my business at all. I signed up for a Google Cloud Security summit, and afterwards a sales rep reached out me. It was obvious from the sta…

"I even made them a schematic of our architecture on GCP at their request."

>> Hahah. They did that to me too. I doubt they even looked at it. It was a fun homework assignment though.

"Once I provided that to them I was met with radio silence."

>> Hahaha. Same here.

"which will inevitably devolve into the discussion of how can I use BigQuery"

>> This is a trap. Once you are on BQ there is no sane way off.

Re: Google Cloud vs. AWS Onboarding Comparison

#124
post #2

Title should maybe be switched to "Google Cloud vs AWS Onboarding Comparison for YC companies". Not to say that isn't a useful article on its own, but it's hard to draw too many meaningful conclusions for the rest of us when the first line of the AWS bullet points is "reach out to dedicated YC email".

Yeah, I think having a YC dedicated mail address at AWS helps. As I am still waiting for a response from AWS regarding joining one of their programs while GCP response was within the day. All access sorted the next day.

Re: Google Cloud vs. AWS Onboarding Comparison

#125
post #77

I've used GCP to great success (with some speedbumps) at 3 companies I've worked for (small and large) over the last 5-6 years. I have a lot of learnings from the experiences to pass on, and one of the key ones is this: work with a reseller. If you've lurked on HN over the past decade you'll have seen tons of stories about how bad Google's customer support is. I don't think GCP's support is anywhere near as terrible…

Thanks for the tip. What I don’t understand is why GCP can’t get customer support right but resellers can. You’d think Google would have more resources than a reseller to provide better service. Is it the size of the company? Company culture?

Re: Google Cloud vs. AWS Onboarding Comparison

#126
post #56

Hi Kevin ;-) I am founder of another YC backed company. We based our startup on GCP infra. They have great tech (for the most part) but I regret it so deeply for two reasons: Support or desire to help customers is non-existent. For any questions, they want us to upgrade to paid support and pay them at least 10% more every month for that (we ask like 1-2 questions a year). What? We are already paying you thousands of…

Eh. It’s similar in AWS-land. Basic business hours support is $29/month or 3% of your service spend, whichever is greater. 24/7 is $100/mo or 10%, which also includes outage assistance. I’ve also worked for places with enterprise support ($15,000/mo or 10%) but of you’re bringing in millions per month it’s definitely worth it. The AWS personal health dashboard is also pretty reliable. The public status page is the so…

Thanks for adding the AWS perspective.

I guess grass is not greener on the other side. Oligopolies for the loss.

Re: Google Cloud vs. AWS Onboarding Comparison

#127
We've been using GCP for a couple of years now and have nothing but good things to say about it. We also used Azure and AWS before migrating to Google, and the whole GCP platform feels a lot more intuitive. Lacking in some areas, sure, but more than makes up for it in other areas like Kubernetes. We had to use support a handful of times for various issues ranging from technical to general billing questions to long term commitments, and all incidents were handled quickly and professionally.

Re: Google Cloud vs. AWS Onboarding Comparison

#128
post #5

Earlier quoted context omitted.

This is also pretty specific about needing more free credits than GCP provides out of the box. If you just want to get started with GCP, you just sign in with your Google Account for $300 in credit. When you run out you can just start paying with a credit card.

Exactly. Google: gives me $300 of credit no questions asked and tells me what things will cost upfront. AWS: makes me apply to a program to get credits and if I want to price out anything it's almost a full-blown research effort where I have to dig through documents and cross reference tables between different services and I still probably miss something important. Free tier is opaque enough to frustrate even "use it…

I don't really agree with that comment. I think all of the megaclouds have undesirably complex pricing structures, but they also all provide pricing calculators. AWS has one here: https://calculator.aws/

If I punch in the services I want to use, I can quickly see how much they will cost, and it's easy. I recommend clicking "Advanced" inside services on the calculator if you want to be sure you're not going to run into an edge case that costs lots of money unexpectedly.

If you use any of the megaclouds without first understanding the price structure, good luck.

Personally, I think a lot of companies would be better off using DigitalOcean or some other medium-size cloud. The pricing is much simpler, and pretty much all medium-size clouds charge $0.02/GB for egress bandwidth, either globally or in the US, depending on the provider.

In contrast, the megaclouds make shocking amounts of money off of their extremely pricey egress bandwidth, among other highly profitable aspects of their business.

Even still, AWS is a solid cloud platform, and they really do seem customer obsessed compared to what I've seen happen on GCP.

Re: Google Cloud vs. AWS Onboarding Comparison

#129
post #15
post #7

Earlier quoted context omitted.

Why? Why can't Google offer the same thing?

Of course Google could offer the same thing. My proposed title change would be even more recommended in that case. My point is that obviously AWS thinks that on average being in YC is going to result in more revenue for them and therefore they prioritize support for YC companies. As a non-YC company I won't get the same treatment which makes any conclusions from this article less useful.

I don't think it's surprising at all that an article posted on a Ycombinator.com subdomain about news talks about Ycombinator-related topics.

Re: Google Cloud vs. AWS Onboarding Comparison

#130
post #56

Hi Kevin ;-) I am founder of another YC backed company. We based our startup on GCP infra. They have great tech (for the most part) but I regret it so deeply for two reasons: Support or desire to help customers is non-existent. For any questions, they want us to upgrade to paid support and pay them at least 10% more every month for that (we ask like 1-2 questions a year). What? We are already paying you thousands of…

Eh. It’s similar in AWS-land. Basic business hours support is $29/month or 3% of your service spend, whichever is greater. 24/7 is $100/mo or 10%, which also includes outage assistance. I’ve also worked for places with enterprise support ($15,000/mo or 10%) but of you’re bringing in millions per month it’s definitely worth it. The AWS personal health dashboard is also pretty reliable. The public status page is the so…

I don't know about Google's support offerings. But when I worked for a startup that was on AWS, here's what we'd do:

1.) Try to figure things out ourselves 2.) If we can't figure it out, subscribe to AWS Support. 3.) Get question answered and then turn off the support plan.

You'll have your support plan for the rest of the month and pay a prorated amount for the days during which you had support. It's quick and cheap.

Post reply on HN