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…
Node.js on Google App Engine Goes Beta
41–50 of 114 posts
Re: Node.js on Google App Engine Goes Beta
#42What version of node is supported? Currently in all other languages they are usually a major version behind (in everything).
You can specify whatever version of Node.js you want to use in the engines section of your package.json: https://cloud.google.com/nodejs/resources/runtime#engines
Re: Node.js on Google App Engine Goes Beta
#43Re: Node.js on Google App Engine Goes Beta
#44Earlier quoted context omitted.
You can specify whatever version of Node.js you want to use in the engines section of your package.json: https://cloud.google.com/nodejs/resources/runtime#engines
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?
Re: Node.js on Google App Engine Goes Beta
#45Don'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…
2014 App Engine is also different from 2016 App Engine, hopefully a lot of the problems you had have been addressed.
(I work for Google Cloud Platform)
Re: Node.js on Google App Engine Goes Beta
#46Don'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…
Last year I moved a personal project (https://www.gitignore.io) over to Heroku and it's been awesome. My whole application runs in memory on a single free dyno. the service uptime has been great and Heroku's pipeline system (Which is basically like Amazon's internal pipeline system) is really good for testing in staging and then going to production.
Re: Node.js on Google App Engine Goes Beta
#47The platform has a lot of quirks, and I had to do a lot more learning than I expected to get the fairly simple project done. But once it was up, it did it's thing.
I'd definitely recommend for free hosting internal applications and personal projects that are just for you to use. Just understand that you'll need to shape your application around the wierdnesses of the platform.
Re: Node.js on Google App Engine Goes Beta
#48I'm surprised they didn't have it until now...
Re: Node.js on Google App Engine Goes Beta
#49is 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…
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)
Re: Node.js on Google App Engine Goes Beta
#50Don'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…
You may want to take a look at Managed VMs. All of the new runtimes are based on Docker images, are entirely extensible, and don't require the use of the original App Engine APIs:
https://cloud.google.com/appengine/docs/managed-vms/
You can use whatever Database or NPM modules you want.