Live data from Hacker News

GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

thehftguy.com

1–10 of 179 posts

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#3
post #2

> AWS Premium Support is mandatory Is Google Cloud support even acceptable? Google is known for poor or no support for most services.

Actually it's surprisingly good. We use them a lot and even when we were on the silver package (the cheapest) they were pretty quick (under 1 hour for P1 situations [production is impacted]).

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#7
We moved back and forth between AWS and GCE (based on who gave us free credits). Once we ran out, we chose GCE and never regretted it.

GCE has many quirks, for instance the inconsistency between API and the UI, it misses the richness of the services offered by AWS but everything GCE does offer is just faster, more stable and much more consistent.

One of the biggest problems with AWS is that once you outgrow the assigned limits, it becomes a hell to get more resources from them. We're running on average around 25k servers a day, majority of them preemptible (spot). AWS requires that you request exact type and location for your instances. GCE only asks for a region and then overall resources (e.g. number of CPUs).

Also the pricing is much less complicated. 1 core costs y, 32 cores cost 32*y.

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#8
AWS premium support is the best support experience I have encountered so far and should absolutely factor into choosing a cloud provider. Reading frequent stories of Google support nightmares across all their services makes me think twice about using GCE. GCE must find a way to counter this.

Also, the AWS premium support fee is negotiable for some customers from what I have heard. They don't like to negotiate down, though!

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#9
post #6

What reason is AWS premium support mandatory? I ask because I'm currently building out SaaS offering on AWS and haven't yet hit any issues requiring support. Can I expect to start seeing issues as traffic scales up to a certain level?

I consider it mandatory because of the various random issues you will face, even without high levels of traffic. Also, when leveraging new features many times the documentation isn't as refined (e.g. the ALB when it first came out). Support is valuable in explaining how to really do something without wasting much time.
Post reply on HN