Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

thehftguy.com

Post reply on HN
Print view View original

171–179 of 179 posts

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

#171

Post by user5994461 »

doh wrote: post #159
user5994461 wrote: post #151

Earlier quoted context omitted.

The "reply" button sometimes goes away when the discussion is deep enough. Gotta click the comment to comment. I would imagine that rolling a container to thousands hosts may take a while. What kind of load and software do you run? In my experience, dramatically scaling out increases load and latency variance and cause all kind of problems. When was your experience with SoftLayer? Care to elaborate? I've got some int…

You're still thinking about these servers as a bare metal. We don't keep the servers running. We create a server always from scratch or based on an image we prepared or with a docker container that is automatically pulled from an internal repo once the OS is turned on. This is the benefit of running on GCP. We don't have to trouble ourselves with the headache of scaling both with the images and containers thanks to t…

Pulling a 100 MB docker image from 1000 hosts would take an eternity.

I stopped thinking about bare metal a while ago. I'm thinking about the comparison with AWS and I see that your entire business is relying on capabilities only available on Google Cloud (which indirectly, is why I'm advising Google Cloud nowadays. It's easier for basic usage and it's unlocking a whole new set of extreme usage).

Things you couldn't have pulled off on AWS that easy: Create thousands of hosts, deploy images that fast, managed kubernetes, pubsub, worldwide AMI, multi region subnets.

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

#172

Post by vgt »

doh wrote: post #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 assig…

Your post has motivated me to blog some details about the difference between AWS EC2 Spot Instances and Google Cloud's Preemptible VMs:

https://medium.com/@thetinot/google-clouds-spot-instances-wi...

(work at Google Cloud)

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

#173

Post by GordonS »

rahrahrah wrote: post #93
GordonS wrote: post #72

Earlier quoted context omitted.

Hah, Adwords must be an exception then - support is total crap. You're lucky if you get a canned response that doesn't begin to answer your question..

Hmm sounds like you might have to increase your bids.

We already pay around $5 per click - I think that's more than enough! However, it's true our business is tiny compared to that of large corporations - but I don't think that excuses the abysmal 'support' I and others have received from Adwords.

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

#174

Post by doh »

user5994461 wrote: post #171
doh wrote: post #159

Earlier quoted context omitted.

You're still thinking about these servers as a bare metal. We don't keep the servers running. We create a server always from scratch or based on an image we prepared or with a docker container that is automatically pulled from an internal repo once the OS is turned on. This is the benefit of running on GCP. We don't have to trouble ourselves with the headache of scaling both with the images and containers thanks to t…

Pulling a 100 MB docker image from 1000 hosts would take an eternity. I stopped thinking about bare metal a while ago. I'm thinking about the comparison with AWS and I see that your entire business is relying on capabilities only available on Google Cloud (which indirectly, is why I'm advising Google Cloud nowadays. It's easier for basic usage and it's unlocking a whole new set of extreme usage). Things you couldn't…

Never tried it on AWS so can't comment on that. It works very well on GCP however. We send over 1M request to their API to rescale the stack every single day (they had to up our limits because it was always timeouting on us).

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

#175

Post by paulddraper »

mdekkers wrote: post #154
paulddraper wrote: post #124

Earlier quoted context omitted.

That is hard to believe. Their case studies have organizations using thousands or tens of thousands of servers for scientific computing, etc.

Case studies tend to be written by the marketing team, and will tell you what the marketing team wants you to believe. I'll take "hey, this is my hands-on experience" over "this is what we want you to think" everytime.

I understand spin, but the claim is that AWS markets a service/product that they will not provide.

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

#176

Post by rahrahrah »

GordonS wrote: post #173
rahrahrah wrote: post #93

Earlier quoted context omitted.

Hmm sounds like you might have to increase your bids.

We already pay around $5 per click - I think that's more than enough! However, it's true our business is tiny compared to that of large corporations - but I don't think that excuses the abysmal 'support' I and others have received from Adwords.

It's a joke... you said that you always get a canned response, didn't you? That's the canned response I always get from them. Doesn't matter what the issue is, raising bids is always the solution.

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

#177

Post by themihai »

aluminussoma wrote: post #14
themihai wrote: 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?

If you are after the raw price you should sign up for bare metal and install/manage your own tools. When you sign up for a service such AWS you pay mostly for the tools/ecosystem and management. I think AWS is still the undisputed leader in that regard, closely followed by Azure. GCP is something I would not recommend due some personal experiences namely the appengine platform and early cloud sdk releases.

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

#178

Post by manigandham »

user5994461 wrote: post #74
imafish wrote: post #24

Earlier quoted context omitted.

Also, GCE is a service while AWS is a suite of services. The correct comparison should be Google Cloud Platform (GCP) vs AWS. Guess it's nitpicking.. but still.

I don't think this is nitpicking. This is probably the single biggest issue with Google right now: Don't know how to call their services. GCE - GCP - Google Cloud - Google Compute Engine - Google Cloud Platform ??? I can see on that blog's analytics that people are looking for various terms which result in different articles and ranking. This needs to be unified by Google. Personally, I think I'm gonna call everythin…

It is unified, they have some of the simplest naming. GCP is Google Cloud Platform which is the entire ecosystem. GCE is Google Compute Engine which is the VM/IaaS offering within.

You can look at the official products page for all the names and descriptions: https://cloud.google.com/products/

Post reply on HN