Live data from Hacker News

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

thehftguy.com

11–20 of 179 posts

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

#11
This was referenced in the previous thread, but here is what amounts to a stl;dr:

> "Unfortunately, our infrastructure on AWS is working " > "I learned recently that we are a profitable company, more so than I thought. Looking at the top 10 companies by revenue per employee, we’d be in the top 10."

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

#12
post #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]).

Can you help me understand how much you define "a lot"? Is it about 2 tickets a month, or more?

With AWS we do have a direct line to a Technical Account Manager which we utilize for the rare P1 (Prod down) situations. That gets things moving quickly if it wasn't already moving quickly with Support.

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

#14
post #4

GCE has its own issues. The raw price is different than the real/total cost. In a better world you shouldn't have to choose between just a few cloud peoviders.

How have you observed the total cost being different from the raw price? In what ways were you surprised?

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

#15
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?

Contrary to what the article says, my company does a lot of business and traffic via AWS and have never once needed support in the last two years.

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

#16
post #3

Earlier quoted context omitted.

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]).

Can you help me understand how much you define "a lot"? Is it about 2 tickets a month, or more? With AWS we do have a direct line to a Technical Account Manager which we utilize for the rare P1 (Prod down) situations. That gets things moving quickly if it wasn't already moving quickly with Support.

You have the same thing for gold and up on GCE. On the rare occasions I have to use it, I get every pennies worth.

Also with P1 issues on GCE most of the time an enginner assigned to the case calls me. I've even spoken directly to the head of google cloud platform via hangouts.

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

#18
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?

We've been on AWS since 2009, and never needed support.

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

#19
post #3

Earlier quoted context omitted.

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]).

Can you help me understand how much you define "a lot"? Is it about 2 tickets a month, or more? With AWS we do have a direct line to a Technical Account Manager which we utilize for the rare P1 (Prod down) situations. That gets things moving quickly if it wasn't already moving quickly with Support.

Just checked, we're on two tickets a week. Sounds a lot but we push GCE to its limits.

On gold support and P1 there is usually an engineer assigned to the ticket. In many occasions you're talking to the person fixing your problem.

GCE is not perfect and neither is their support. But they do try and even when things go sidewise they take responsibility for it, which didn't happen much with AWS, at least in our case.

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

#20

I really like OVH's SoYouStart in terms of its pricing for CPU/memory intensive computations, their prices just destroy AWS/GCE: https://www.soyoustart.com/ca/en/essential-servers/

Really bad support. And if you get packetstormed, they just nullroute you and call it "DDoS protection".

Over the years, I've had plenty enough of ovh/kimsufi/hetzner/etc.

For dedicated, I favor online.net and their alternative brand scaleway. Else AWS. I haven't played with GCE yet.

Post reply on HN