Live data from Hacker News

Google Cloud vs. AWS Onboarding Comparison

kevinslin.com

331–340 of 394 posts

Re: Google Cloud vs. AWS Onboarding Comparison

#331
Google Cloud needs to hit the numbers. And the only way to do this is to hit the big boys. Dealing with 1000 small customers who are petty and spending small vs dealing with 1 big customer that moves the needle. That is what is going on here.

Once Google Cloud manages to hit the numbers, you would expect things to be much better for the smaller players (this remains to be seen).

Not excusing their support operations, but I did manage to get on chat with someone about a Billing issue (to understand my billing better), and I was pleasantly surprised at the response time (immediate).

The slow and free support route is to use the Google Cloud issue tracker: https://cloud.google.com/support/docs/issue-trackers You tend to use this if you are not critically impacted and you are also a developer.

By and large, things works as advertised. You can keep spamming that Feedback form in the Cloud Console. Product Managers do read it and address it.

Re: Google Cloud vs. AWS Onboarding Comparison

#332
post #158

Earlier quoted context omitted.

Huh? Please look at the actual AWS page: https://aws.amazon.com/premiumsupport/pricing/ Developer support $29/month, and business support is $100 (both go up if you spend more). I paid for business support. You get 24x7 phone, email, and chat access to Cloud Support Engineers Unlimited cases / unlimited contacts (IAM supported) This is for $100/MONTH!! That is the deal of the century. And they are ridiculously helpfu…

The price starts to go up steeply once you hit the % of monthly spend. I'd guess they don't get many resource intensive support queries from the < $10k a month customers (and at that level you probably don't get the A team support)

Another comment later identified this - I actually did get a weirdly A-team support response. That's what made me scratch my head because I was coming in the poor / cheap / don't know what they are doing door (and most support is crap user misconfig issues at least from my experience). I just wanted the thing noted somewhere in case others were hitting it, instead I got a way above standard support specific technical response and some suggestions.

The other poster indicated it is possible for stuff like this that you get bumped, even on the el cheapo plan, to someone actually on product team. While I'd hate to be on the product team having to answer these, it perhaps keeps folks aware of customer issues so they can at least improve docs for corner cases?

Re: Google Cloud vs. AWS Onboarding Comparison

#333

Earlier quoted context omitted.

What makes GCP's Kubernetes offering better than the competition?

There are several reasons: - Google has a lot of experience running containerized services because of Borg. Google Research says that they have been running these workloads since 2005. - The above gives them insight into how to do this well. They would have the internal infrastructure, logging and monitoring already setup. - They are the creator and still a major contributor to Kubernetes itself which means they can…

The Borg thing is pure marketing.

Amazon also has been running internally on containers for years before ECS. But workloads for massive FAANG companies designed by FAANG engineers turn out to be quite different than most AWS/GCP customers.

Just like EC2 wasn't Amazon selling its "spare capacity during off-peak" but always a purpose built service with completely isolated data centers and network fabric from day 1, the connection between Borg and Kubernetes is tenuous at best.

Honestly, I would encourage you to evaluate ECS and Fargate. Forget Kubernetes and direct instance management. Try a construct like https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws... and see how much simpler it is than all the K8S overhead.

Source: I'm at Amazon but I work on none of these services and opinions are my own. I played with K8S and am eternally confused how it's as popular as it is. I guess it gives you the illusion of not having lock in?

Re: Google Cloud vs. AWS Onboarding Comparison

#334

Earlier quoted context omitted.

Hit me, more than happy to make fun of the salient GCP rep for you in a way they really won't like :)

Bit of a surprising comment coming from the CTO of a large Google partner? https://sada.com/about/leadership-team/miles-ward/

What do you think partners are for if not this?

Re: Google Cloud vs. AWS Onboarding Comparison

#335

Earlier quoted context omitted.

Aurora is one of the DB things you can launch in RDS.

Thanks for clarifying. I'd associated RDS with the non-Aurora offerings of Mysql and Postgres. Judging by upstream version compatibility it appears Aurora is more heavily forked than their non-Aurora siblings.

I don't think Aurora MySQL/Postgres are just forks, I think they are a completely custom datastore behind a MySQL or Postgres-compatible interface (which probably uses a lot of non-engine code from the open-source base database.)

Re: Google Cloud vs. AWS Onboarding Comparison

#336
post #322
post #35

Earlier quoted context omitted.

Google will suspend entire accounts even if you have more than one owner. A few years back, our business credit card was somehow stolen and used to buy Google Adwords. We disputed the charge with our bank. A day or two later, at 4am local time, our GCP account was suspended for fraud (presumably because the same, stolen, card was attached to that account). All instances were stopped and our service was brought to a h…

Googler, opinions are my own. We actually created a portal where you can report unknown charges to Google directly; https://payments.google.com/payments/unauthorizedtransaction... Credit card companies tell you to work with a company before issuing a chargeback, as chargebacks are a last resort. The above form helps you keep you account active without being swept up in the chargeback process. It's something we all wa…

I believe that the "work with a company" guidance is for a dispute (e.g. you ordered something, but didn't get it or are otherwise unhappy) -- not an outright unauthorized purchase by someone other than the card holder. I don't see what most companies would do if you approached them in this case: you have no order number, no information about the purchase, nothing to return, etc.

The only logical thing to do in the case of a stolen or copied card is to contact the bank directly, so that the card can be canceled and fraudulent charges reversed.

Re: Google Cloud vs. AWS Onboarding Comparison

#337
post #322

Earlier quoted context omitted.

Googler, opinions are my own. We actually created a portal where you can report unknown charges to Google directly; https://payments.google.com/payments/unauthorizedtransaction... Credit card companies tell you to work with a company before issuing a chargeback, as chargebacks are a last resort. The above form helps you keep you account active without being swept up in the chargeback process. It's something we all wa…

I believe that the "work with a company" guidance is for a dispute (e.g. you ordered something, but didn't get it or are otherwise unhappy) -- not an outright unauthorized purchase by someone other than the card holder. I don't see what most companies would do if you approached them in this case: you have no order number, no information about the purchase, nothing to return, etc. The only logical thing to do in the c…

Point taken. I thought of that same point after I wrote the above.

Re: Google Cloud vs. AWS Onboarding Comparison

#338

Earlier quoted context omitted.

Thanks for clarifying. I'd associated RDS with the non-Aurora offerings of Mysql and Postgres. Judging by upstream version compatibility it appears Aurora is more heavily forked than their non-Aurora siblings.

I don't think Aurora MySQL/Postgres are just forks, I think they are a completely custom datastore behind a MySQL or Postgres-compatible interface (which probably uses a lot of non-engine code from the open-source base database.)

Regardless it looks like anyone choosing Aurora should not hold their breath for Mysql 8 or Postgres 10+ compatibility. Seems like only one major version bump has happened since they launched the first one (Mysql 5.6-to-5.7).

Which is fine. It can just be a little confusing as they drift and the caveats grow.

Re: Google Cloud vs. AWS Onboarding Comparison

#339

Earlier quoted context omitted.

It's a full-company culture problem where ~everyone has personal responsibility. Behavioral properties are end-to-end, like speed, security, customer success, uptime, etc. Everyone and everything on the hotpath for that has to be on board, as just one violator means nobody is achieving it. Operationally, part of achieving that means company norms, such as when collaborating, planning, executing, etc. It's 100% fine n…

I tried explaining this to some Azure product teams, and they gave me a blank stare in return. Sure, you can have zone-redundant Azure SQL Databases, but not Azure App Service! You can have zonal Azure App Service, but with a different network model than the default, so it's a breaking change for some apps. It's as if nobody has actually sat down at Microsoft to build something similar to what their customers are bui…

My experience with MSFT is that the account reps are clueless by design. Even the sales assistants with fancy technical titles are short of clues. Easier for them to oversell when they don’t know what’s really going on underneath. We have to go 3 or 4 deep into their product org to find someone who will fess up to product issues that we are already aware of.

Re: Google Cloud vs. AWS Onboarding Comparison

#340

Earlier quoted context omitted.

I don't think Aurora MySQL/Postgres are just forks, I think they are a completely custom datastore behind a MySQL or Postgres-compatible interface (which probably uses a lot of non-engine code from the open-source base database.)

Regardless it looks like anyone choosing Aurora should not hold their breath for Mysql 8 or Postgres 10+ compatibility. Seems like only one major version bump has happened since they launched the first one (Mysql 5.6-to-5.7). Which is fine. It can just be a little confusing as they drift and the caveats grow.

> Regardless it looks like anyone choosing Aurora should not hold their breath for Mysql 8 or Postgres 10+ compatibility.

Current Aurora Postgres is compatible with pg 12.4; pg 10+ support has been around so long that several versions that support 10+ have already been EOL’d by Amazon. Even Serverless, which lags behind, is on 10.x.

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide...

Post reply on HN