Best IT Recipes

Why is javascript node.js missing in google app engine

Google has created the JavaScript engine V8: V8 compiles JavaScript source code directly into machine code when it is first run.

Node.js is built on V8 - why doesn't Google offer any Node.js servers like Microsoft Azure?

The Google App Engine will be the natural place to host Node.js.

Do you know why Google is not doing this?

+70
google-app-engine
Sep 16 '12 at 20:08
source share
11 answers

As of June 2014, Google had a limited preview of user languages ​​in the Google App Engine (which is different from the Google Compute Engine) .

Check out the assembly of Node.js apps using the App Engine and custom runtimes and see https://cloud.google.com/appengine/docs/managed-vms/ :

App Engine now offers a second hosting option: managed virtual machines. The managed virtual machine hosting environment allows you to run App Engine applications on custom Compute Engine virtual machines. You can also use managed virtual machines to deploy custom user- defined runtimes such as Node.js and other runtimes.

Beta Login Procedure:

Register and create a managed virtual machine project

Managed virtual machines are in preview mode, you must register to access this function, create a project with billing support, and tell us about your project so that we can whitelist it to run on a managed virtual machine. Follow these steps:

  1. Register to access managed virtual machines.
  2. Join the Google group app-engine-managed-vms to participate in discussions about managed virtual machines.
  3. Projects (or applications - this is one and the same thing) should be located in a data center in the USA. If you plan to use an existing project, proceed to the next step. Otherwise, create a new application in the US data center. Go to https://preview.appengine.google.com and create a new application.
  4. Enable billing for the project. Visit https://cloud.google.com/console/project/apps~ where your project ID is located. Click "Settings" in the left menu, and then enable billing. If your application is paid with a Premier account, write to us at app-engine-managed-vm-tt-id@google.com so that your new cloud project will be billed with the same account.
  5. Send an email to app-engine-managed-vm-tt-id@google.com with the app ID in the subject line.

When we receive your email, set up some resources backstage and notify you by email when your project is ready to go. The letter contains the latest setup instructions. If you encounter an error while following these instructions, please contact us at app-engine-managed-vm-tt-id@google.com.

+32
Jun 26 '14 at 9:48
source share

Node.js is supported by Joyent, a competitor to Google.

Node.js has no connection with Google, but is actually built on the basis of an open source project launched by Google.

Google can start this business just like Azure did, but PaaS is already doing so much that it might not be worth it. I have never used GAE, but as I understand it, it is very different from other PaaSs, and you must use the GAE libraries for your code to work.

Which, in my personal feelings, is not quite what the Node.js. community is looking for Node.js is used to quickly create a lightweight application, for example, a large proportion of the APIs for Phone applications.

However, if you are looking for PaaS for Node.js, there are many:

These are just some of the names from my head. There are many of them, but these are the main ones. Oh, there is Heroku , but they don’t have WebSocket support, which is a bummer for any Socket.IO-based application.

+40
Sep 16 '12 at 20:10
source share

You can easily install the node on the Google Compute Engine (which is basically a virtual computer). Here is the link: https://developers.google.com/datastore/docs/getstarted/start_nodejs/

Regards Lars

+23
Sep 15 '13 at 20:54 on
source share

After years of working with Google Appengine, I switch to other cloud services.

I think Google Appengine is actually an old service in the cloud computing industry. which is slow for new technologies, difficult to deploy, a waste of time learning the API and lacking many of the features you need in the languages ​​you use.

Regardless of the large Google community, I would not advise anyone to use the Google Appengine.

[new paas]

I highly recommend you use openshift, appfog, heroku.etc and new paas cloud computing technologies that are much more extensible, require fewer changes, more portable from one platform to another, more freely encode the beauty of the natural language and its library standard without the ugly specific for apis platforms.

[IAAS]

if you need more control over a running OS, you can try lynod, digital ocean, Amazon, Google cloud engine, Microsoft Azure and others.

+21
Jun 25 '13 at 21:58
source share

Because App Engine is a platform as a service, and to add a new language / stack to Google GAE, you need to create mid-level libraries that interact with many App Engine services .

In addition, all App Engine applications are in a sandboxed environment and have several features that are limited within their sandbox environment. This means that besides the need to create Google service libraries, it is also necessary to create a secure sandbox environment for any language / stack that they are trying to implement in GAE.

I personally think the second reason is that Google is not introducing support for the new language / stack as aggressively as in Azure. App Engine, in a sense, is more "manageable" than Azure, and has a large initial development cost for a new language / stack.

+13
Sep 16
source share

Node.js recently turned on Google Cloud user support. The main pages of the document:

It seems that an instance of the Compute Engine is currently required.

+3
Aug 25 '14 at 11:32
source share

Released as of March 2016.

https://cloudplatform.googleblog.com/2016/03/Node.js-on-Google-App-Engine-goes-beta.html

+3
Mar 27 '16 at 11:14
source share

Background: App Engine vs. Flexible App Engine

There seems to be some confusion about this topic, because there are two versions of App Engine: Standard and Flexible. NodeJS is supported in App Engine Flexible, but NOT in the App Engine standard. (See here for a more complete explanation of the differences.)

App Engine Standard scales in seconds (as opposed to minutes for a flexible environment) and has a free tier so you can develop and demonstrate without spending a dime. These benefits are achieved through flexibility. App Engine Standard supports only certain languages ​​and libraries, does not allow writing to disk and SSH. In other words, the environment is standardized.

Answer: NodeJS support in the App Engine standard

If you are interested in supporting NodeJS in App Engine Standard , flag this issue as follows: https://issuetracker.google.com/issues/67711509 .

Google addresses features that grab community attention (see here ). The best way to draw your attention to this feature is to add it to the Google Issue tracker above.

+3
Nov 14 '17 at 22:16
source share

March 21, 2016 Google announced that the beta version of Node.js on the Google App Engine: https://cloudplatform.googleblog.com/2016/03/Node.js-on-Google-App-Engine-goes-beta.html ? m = 1

This was expected since Google also joined the Node.js Foundation, and Google is developing a V8 JavaScript engine that supports Chrome and Node.js: https://nodejs.org/en/blog/announcements/welcome-google/

Google announced a partnership with NodeSource at the same time.

+1
Jun 13 '16 at 6:50
source share

Google has just announced support for Node.js in the App Engine.

enter image description here See: https://cloud.google.com/nodejs/

Here's an example of how to deploy a Node.js app on App Engine .

+1
Jun 13 '18 at 5:55
source share

Google is a conservative software company. JavaScript backend programming would be completely unimaginable for Google managers. Creating an infrastructure that Google will not use is not a good investment. Link: Notes from the Mystery Machine Bus

0
Dec 14 '14 at 17:27
source share


More articles:


All Articles