> "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."
GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
11–20 of 179 posts
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#12> 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]).
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
#13Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#14GCE 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.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#15What 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?
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#16Earlier 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.
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
#17> AWS Premium Support is mandatory Is Google Cloud support even acceptable? Google is known for poor or no support for most services.
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#18What 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?
Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon
#19Earlier 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.
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
#20I 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/
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.