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

Node.js on Google App Engine Goes Beta

cloudplatform.googleblog.com

Post reply on HN
Print view View original

51–60 of 114 posts

Re: Node.js on Google App Engine Goes Beta

#51

Post by jorgecurio »

adrianpike wrote: post #32
jorgecurio wrote: post #30

is anyone using node.js in enterprise? because everyone seems to be convinced that the enterprise companies are going to uproot all the network of partners, developers, vendors, and billions of dollars of investment made over the past decade? Like it or not, JVM pretty much rules the enterprise space and there's just no way to do it another way. Literally, you will be turned away because you told the IT department th…

Yes, we are, but caveat; it's only for a few smaller services where the functionality makes lots of sense to be heavily asynchronous, and we're not leveraging many external dependencies. FWIW, deployment and packaging is still a painful issue for node - I've been bitten in the past by people not semver'ing their modules in a non-breaking way.

thanks I think that is a more realistic real world scenario, some people on HN thinks they can change the enterprise world but it's super hard to do it with javascript imho and evident by that it's not being used in wide deployment....

Java is still king in the enterprise world.

Re: Node.js on Google App Engine Goes Beta

#52

Post by jorgecurio »

sehr wrote: post #49
jorgecurio wrote: post #30

is anyone using node.js in enterprise? because everyone seems to be convinced that the enterprise companies are going to uproot all the network of partners, developers, vendors, and billions of dollars of investment made over the past decade? Like it or not, JVM pretty much rules the enterprise space and there's just no way to do it another way. Literally, you will be turned away because you told the IT department th…

it irks me when a 19 year old CTO on the autistic spectrum This added literally nothing to your post aside from a nice dose of ableism. This is HN, not reddit (if that still means anything these days)

you add nothing to the discussion on whether you are using node.js in enterprise or not. feel free to nit pick further by adding nothing to the discussion.

reply to the other guys comment below:

what's a BRE?

true but a bulk majority of businesses (fortune 10,000) are built on some type of Java. I just don't see them uprooting their investments.

It's always easier to think of tearing things down then building on top of existing,stable and mature systems like JVM. So much of the worlds devices and critical applications depend on JVM. I just don't see it changing in the manner poeple on HN will have you believe. One unicorn at a time guys...

Re: Node.js on Google App Engine Goes Beta

#53

Post by mvitorino »

mattbillenstein wrote: post #31

Don't use AppEngine. I migrated Homejoy off of AppEngine in 2014 and I can't recommend the platform for any reason whatsoever. It's slow, expensive, not based on OSS, and not particularly stable. Bits of it (urlfetch, search, etc) would go down for hours at a time and you're basically hosed until they fix it. I think Heroku is usable with a similar level of effort -- and you have a much easier migration path to somet…

I do have plenty of production experience with GAE and is very different from yours. But our experience is from 2014. Since that period we were only affected by a single outage, on the 6th of Dec 2015 related to Google authentication against it's apis for around 17h.

Google seems to be giving a lot of love to GAE recently, especially with Managed VMs. They have delivered substancial improvements to the reliability of the platform.

EDIT: note that the issue I mentioned only affected 1.29% of the apps on GAE according to Google.

Re: Node.js on Google App Engine Goes Beta

#54

Post by boulos »

esilverberg2 wrote: post #43

I wrote about my (unsuccessful) app engine experience many years ago...hopefully they've improved since then. http://www-cs-students.stanford.edu/~silver/gae.html

Good writeup! I think the main change is that App Engine has really morphed into a "You know, you don't have to use Datastore". Cloud SQL was added precisely because of the issues you raise: being on App Engine meant being in a totally foreign world, and not being able to get out easily.

If you were to try again today, you'd take stock Django 1.9 via pip install Django -t lib and using vendoring: https://cloud.google.com/appengine/docs/python/tools/librari... . You point it at your Cloud SQL instance in your DATABASES line (https://cloud.google.com/appengine/docs/python/cloud-sql/dja...) and you're done.

tl;dr: Yep! Things have improved in the last 5 years.

Disclosure: I work on Compute Engine.

Re: Node.js on Google App Engine Goes Beta

#55

Post by ionwake »

avar wrote: post #40
ionwake2 wrote: post #25

Earlier quoted context omitted.

Hi, Thanks for the reply. I would like to retract the statement that it was a member of staff, you are correct, this may have not been the case. It was a while ago and it may have just been someone in the know, who didn't actually work for google. I didnt expect anyone to even notice my comment. I should have been more careful with my statements. I will be removing the comment when HN allows me to log back in (appare…

> I will be removing the comment when HN allows me to log back in. In that case, here's a copy of your initial comment, because removing top-level comments that have ongoing follow-up discussion makes for very confusing discussions: > All I know about GAE is that when my python app started being used > by HN users I upgraded my account to a paid one to increase > performance. > > In the transition , without any warni…

Well for some reason I can't seem to be able to delete my comment, so I guess there isn't much I can do =(

Re: Node.js on Google App Engine Goes Beta

#57

Post by baudehlo »

eecks wrote: post #39
ionwake wrote: post #5

All I know about GAE is that when my python app started being used by HN users I upgraded my account to a paid one to increase performance. In the transition , without any warning, google took the app down, for a day. Thus killing all chance of acquiring a userbase now that I had hit the frontpage. When I went onto the IRC GAE channel to ask someone for help to unlock or keep the app running during this important mom…

That is pretty awful. Have you found an alternative that you can suggest?

It's really not that hard to run your own servers (VPS) - it's almost always the best way to control things and they scale up way better than most people think.

But if you're really scared of that, farm out the entire operations system to a company like vmfarms. They'll take care of everything for you. A bit more expensive but they will hold your hand the entire way.

Re: Node.js on Google App Engine Goes Beta

#58

Post by davidjgraph »

So many negative views of GAE, I have to add our, overwhelmingly positive, experience.

We were paying $200/month for a load balanced EC2 setup in 2011, that's for around 2k unique daily users. The load balancer kept on false triggering new instances, so we went to GAE in 2012.

Since then our uptime has been horrifically good, heavily thanks for GAE, trashing that of our competition, who mostly use AWS.

Last month we paid $150 for everything on GAE, traffic, CPU, etc. G-Analytics shows a peak of 54k daily uniques last week. All the scaling is dealt with for us, we can handle literally any traffic peak. i.e. x27 more traffic, lower cost, better uptime, spending virtual zero time looking at the operations side of things.

This is a mission critical app, although, we've never invoked support, so I can't comment on that side.

Re: Node.js on Google App Engine Goes Beta

#59

Post by dlor »

diggan wrote: post #44
BinaryIdiot wrote: post #42

Earlier quoted context omitted.

Frustrating that it doesn't specify how it gets those versions. Is it always direct from the node folks so it's going to always have all versions or do they have their own cache?

Reading the source code of the docker container they use ( https://github.com/GoogleCloudPlatform/nodejs-docker/blob/ma... ) it seems like it's reading the available versions from an URL ( http://storage.googleapis.com/gae_node_packages/node_version... ) which points to some Google hosted storage. So I'm guessing they have some process to update this list after a new release and also caches the versions themselves.

Yep, we update the available versions constantly and just serve them from GCS to reduce download time.

I'll get this documented somewhere.

Disclosure: I work on GCP.

Re: Node.js on Google App Engine Goes Beta

#60

Post by stephenitis »

davidjgraph wrote: post #58

So many negative views of GAE, I have to add our, overwhelmingly positive, experience. We were paying $200/month for a load balanced EC2 setup in 2011, that's for around 2k unique daily users. The load balancer kept on false triggering new instances, so we went to GAE in 2012. Since then our uptime has been horrifically good, heavily thanks for GAE, trashing that of our competition, who mostly use AWS. Last month we…

did software change to account for efficiencies?
Post reply on HN