Well that took forever. Congrats on getting to the right place though Google.
Node.js on Google App Engine Goes Beta
81–90 of 114 posts
Re: Node.js on Google App Engine Goes Beta
#82Wow, I thought that GAE was basically dead and now I find out that, besides the latest addition of Node.js, it supports Python 3, Java 8 and even Docker-based custom runtimes...
Re: Node.js on Google App Engine Goes Beta
#83Earlier quoted context omitted.
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…
They aren't nitpicking, it's a shitty thing to say. Period.
grow a thicker face
Re: Node.js on Google App Engine Goes Beta
#84is 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…
Honestly what is the enterprise these days? Internal apps are getting very quickly replaced by SaaS. Some of them are built on Node.js and many of them aren't. Most of the larger ones are built on a mix of technologies. And so is the enterprise. You'll find it impossible to find a single Fortune 500 company with everything they do in one single stack. It just doesn't happen. Microsoft have Linux services and systems.…
please provide sources and references to back up your claims.
Re: Node.js on Google App Engine Goes Beta
#85Has anyone tried running MeteorJS on GAE?
Re: Node.js on Google App Engine Goes Beta
#86So, considering that it's beta, where should I expect rough edges? Is there any list that shows what's missing to go from beta to full production? I'm actually really interested in trying this out, but I want to know what potential issues I should expect to deal with. Something I found really awesome about Google's services is that they provide fake local implementations that you can run from the CLI. This means that…
In that example we don't need to run the webpack build inside the Docker image when the container is started. There are multiple points in the application deployment lifecycle where a webpack build could be performed.
When you deploy with the gcloud cli a Docker image will be packaged for you and and deployed. You could easily run a webpack build before the image is packaged so the built files get packaged as well, or extend the image with your own Dockerfile to customize the Docker steps, or build the image yourself locally and deploy your already built image, etc...
Re: Node.js on Google App Engine Goes Beta
#87Don'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…
"It's slow, expensive" - That sounds exactly like Homejoy!
Re: Node.js on Google App Engine Goes Beta
#88Don'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 agree. I built a huge python app on AppEngine back in 2009-2012 called Vroomtrap which was an app for tracking speed traps. The BigTable data store wasn't ever designed for multiple inequality queries (e.g. where X is between two points AND Y is between two points -- basically a bounding box) I ended up creating a GeoHashing function but I would have been better off not wasting so much time going down the AppEngine…
[deleted]
Re: Node.js on Google App Engine Goes Beta
#89Don'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…
Datastore isn't proprietary, AppScale (http://www.appscale.com) has built a handy OSS version which runs above Cassandra.
https://github.com/AppScale/appscale
Disclaimer: I work at GCP, so I'm geeked about open approaches to solving problems :)
Re: Node.js on Google App Engine Goes Beta
#90So, considering that it's beta, where should I expect rough edges? Is there any list that shows what's missing to go from beta to full production? I'm actually really interested in trying this out, but I want to know what potential issues I should expect to deal with. Something I found really awesome about Google's services is that they provide fake local implementations that you can run from the CLI. This means that…
This is my understanding about Google Cloud services; - Alpha means sub par quality / rough edges / unresolved issues. - Beta means fairly stable but no SLA, no guarantees from Google. So I'd guess it's fine to use now.
With Google it's either beta or deprecated.