为什么javascript节点。不是在谷歌应用程序引擎上

时间:2023-01-17 15:41:59

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

谷歌创建了V8 JavaScript引擎:V8将JavaScript源代码直接编译为第一次执行的机器码。

Node.js is build on V8 - why is Google not offering any Node.js servers like Microsoft Azure?

节点。js是在V8上构建的——为什么谷歌不提供任何节点。像微软Azure这样的js服务器?

Google App Engine would be a natural place to put Node.js.

谷歌应用程序引擎将是放置Node.js的天然场所。

Do you know why Google is not doing just that?

你知道谷歌为什么不这么做吗?

11 个解决方案

#1


32  

As of June 2014, Google had a limited preview for custom languages on Google App Engine (which is different from Google Compute Engine).

到2014年6月,谷歌在谷歌应用引擎上对自定义语言进行了有限的预览(与谷歌计算引擎不同)。

Watch Building Node.js applications with App Engine and Custom Runtimes and check out https://cloud.google.com/appengine/docs/managed-vms/:

看建筑节点。使用App Engine和自定义运行时的js应用程序,请查看https://cloud.google.com/appengine/docs/managed-vms/:

App Engine now offers a second hosting option: Managed VMs. The Managed VM hosting environment lets you run App Engine applications on configurable Compute Engine Virtual Machines (VMs). You can also use Managed VMs to deploy user-configurable custom runtimes, such as for Node.js and other runtimes.

App Engine现在提供了第二个托管选项:托管vm。托管VM托管环境允许您在可配置的计算引擎虚拟机(VMs)上运行应用程序引擎应用程序。您还可以使用托管vm来部署用户可配置的自定义运行时,比如Node。js和其他运行时。

The procedure to get into the beta is:

进入测试的程序是:

Sign up and create a Managed VM project

Managed VMs are in Limited Preview, you must sign up for access to this feature, create a billing-enabled project, and tell us about your project so we can whitelist it to run in a Managed VM. Follow these steps:

受管理的VM在有限的预览中,您必须注册以访问这个特性,创建一个启用了billing的项目,并告诉我们您的项目,以便我们可以将其在受管理的VM中运行。遵循以下步骤:

  1. Sign up for access to Managed VMs.
  2. 注册访问托管vm。
  3. Join the app-engine-managed-vms Google Group to participate in discussions about Managed VMs.
  4. 加入app-engine- managedvms谷歌组,参与关于托管vm的讨论。
  5. Projects (or apps - they are the same thing) must be in a U.S. data center. If you're planning to use an existing project, skip to the next step. Otherwise, create a new app in a U.S. data center. Navigate to https://preview.appengine.google.com and create a new app.
  6. 项目(或应用程序——它们是一样的东西)必须在美国的数据中心。如果您计划使用一个现有的项目,请跳到下一个步骤。否则,在美国数据中心创建一个新的应用程序。导航到https://preview.appengine.google.com并创建一个新的应用程序。
  7. Enable billing for the project. Visit the page https://cloud.google.com/console/project/apps~, where is the ID of your project. Click on Settings in the left menu and then enable billing. If your app is billed under a Premier account, email us at app-engine-managed-vm-tt-id@google.com to have your new Cloud project billed under the same account.
  8. 支持项目的计费。访问页面https://cloud.google.com/console/project/apps~,你的项目的ID在哪里。单击左侧菜单中的设置,然后启用计费。如果你的应用是在一个主要账户下收费的,请发邮件到app-engine管理的vm-tt-id@google.com,让你的新云项目在同一个账户下收费。
  9. Send an email to app-engine-managed-vm-tt-id@google.com with the application ID in the subject line.
  10. 向app-engine管理的vm-tt-id@google.com发送电子邮件,标题行中包含应用程序ID。

When we receive your email, we’ll configure some resources behind the scenes and notify you via email when your project is ready to go. The email includes final instructions for setup. If you encounter an error while following these instructions, contact us at app-engine-managed-vm-tt-id@google.com.

当我们收到您的电子邮件时,我们将在后台配置一些资源,并在项目准备就绪时通过电子邮件通知您。这封电子邮件包含安装的最终说明。如果您在遵循这些说明时遇到错误,请通过app-engine-managed-vm-tt-id@google.com联系我们。

#2


40  

Node.js is maintained by Joyent, who is in a way a competitor of Google.

节点。js由Joyent维护,Joyent在某种程度上是谷歌的竞争对手。

Node.js has no link what so ever with Google but is in fact built on top of an open source project started by Google.

节点。js与谷歌没有任何联系,但实际上是建立在由谷歌启动的开源项目之上的。

Google might jumped into this business just like Azure did, but there are already so many PaaS doing it, it might not be worth it. I have never used GAE, but my understanding is that it is quite different that other PaaS and you have to use GAE libraries to make your code run.

谷歌可能会像Azure一样投入到这个业务中,但是已经有很多的PaaS做了,可能不值得。我从未使用过GAE,但我的理解是,与其他PaaS和您必须使用GAE库来运行代码是完全不同的。

Which, this is my personal feeling, is not really what the Node.js community is looking for. Node.js is used to quickly make a fast lightweight app, a big share for APIs for Phone apps for example.

这是我个人的感觉,并不是真正的节点。js社区正在寻找。节点。js被用来快速制作一个轻量级的应用程序,比如手机应用程序的api。

Nevertheless if you are looking for a PaaS for Node.js, the are quite a few out there:

然而,如果您正在寻找节点的PaaS。js,有很多

  • Joyent (nodejitsu)
  • Joyent(nodejitsu)
  • dotCloud which has WebSockets support.
  • dotCloud支持WebSockets。
  • Windows Azure
  • Windows Azure
  • Nodester (bought by App Fog recently)
  • Nodester(最近被应用Fog收购)
  • Any Cloud Foundry host should support Node.js too.
  • 任何云的铸造主机都应该支持节点。js。
  • and many more...
  • 和更多的……

Those are just some names off the top of my head. There quite a few but those are the major ones. Oh there is Heroku too, but they don't have support for WebSocket which is a bummer for any Socket.IO based app.

这些只是我脑海里的一些名字。有不少,但那些是主要的。哦,也有Heroku,但是他们不支持WebSocket,这对任何Socket来说都很糟糕。基于IO的应用。

#3


23  

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

您可以在谷歌计算引擎(基本上是一个虚拟计算机)上安装node。这里有一个链接:https://developers.google.com/datastore/docs/getstarted/start_nodejs/

Regards Lars

认为拉斯

#4


21  

after years of experiences in google appengine, i switch to other cloud services now.

在谷歌appengine工作多年之后,我现在转向其他云服务。

i think google appengine is actually an old fashion service in cloud computing industry. which is slow to new technology, difficult to deploy, time wasting to learn the apis and lacking of a lot of features you need in languages you use.

我认为谷歌应用程序引擎实际上是云计算行业的一种老式服务。这对新技术来说是缓慢的,很难部署,学习api是浪费时间,而且在使用的语言中缺少很多需要的特性。

regardless of google's large community, i would not suggest anyone to use google appengine.

不管谷歌的大社区是什么,我都不会建议任何人使用谷歌appengine。

[newer paas]

(更新的paas)

i strongly recommend you to use openshift, appfog, heroku .etc's new paas cloud computing technologies, which are far more extensible, less change needing, more migrable from one platform to another, more freely coding in the beauty of the natural lanuage and its standard libraries without ugly platform specific apis.

我强烈建议您使用openshift、appfog、heroku .etc的新paas云计算技术,这些技术具有更强的可扩展性、更少的更改需求、更易于从一个平台迁移到另一个平台、更*地在自然语言和其标准库的优美环境中编码,而没有难看的特定于平台的api。

[iaas]

(iaas)

if you want more control over the running os environment, you may give linode, digital ocean, amazon, google cloud engine, microsoft azure etc. iaas providers a try.

如果您希望对运行的操作系统环境有更多的控制,您可以尝试使用linode、digital ocean、amazon、谷歌云引擎、microsoft azure等iaas供应商。

#5


13  

Because App Engine is a platform-as-a-service, and in order to add a new language/stack to GAE, Google need to create mid-level libraries that interface with the plethora of App Engine's services.

因为App Engine是一种平台即服务,为了向GAE添加新的语言/堆栈,谷歌需要创建与大量应用引擎服务相连接的中间层库。

Moreover, all App Engine apps is sandboxed and has several functionalities restricted from inside their sandbox environment. This means that beside the need to create service libraries, Google also need to create a secured sandbox environment for any language/stack that they try to introduce into GAE.

此外,所有应用程序引擎应用程序都是沙箱型的,并且有几个功能限制在沙箱环境中。这意味着除了需要创建服务库之外,谷歌还需要为它们试图引入到GAE的任何语言/堆栈创建一个安全的沙箱环境。

I personally think the second reason is why Google does not introduce support for new language/stack as aggressive as Azure did. App Engine is, in a way, more 'managed' than Azure, and has a larger initial development cost for new language/stack.

我个人认为第二个原因是为什么谷歌没有像Azure那样引入对新语言/栈的支持。在某种程度上,应用程序引擎比Azure更“受管理”,新语言/栈的初始开发成本也更高。

#6


3  

It has been released as of March 2016.

该片已于2016年3月上映。

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

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

#7


3  

Node.js has recently enabled support for Google Cloud users. The main document pages are:

节点。js最近支持谷歌云用户。主要文件页为:

It seems to require at the moment a Compute Engine instance.

目前似乎需要一个计算引擎实例。

#8


3  

Background: App Engine Standard vs App Engine Flexible

背景:App引擎标准vs App引擎灵活

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

在这个话题上似乎有些困惑,因为有两个版本的App Engine: Standard和Flexible。App Engine Flexible支持NodeJS,但不支持App Engine标准。(有关差异的更完整的解释,请参见这里)。

App Engine Standard scales in seconds (as opposed to minutes for the Flexible environment), and has a free tier, so you can develop and demo without spending a dime. These benefits come at the cost of flexibility. App Engine Standard only supports certain languages and libraries, doesn't allow writing to disk nor SSH. In other words, the environment is standardized.

应用程序引擎标准以秒为单位伸缩(与灵活的环境不同),并且有一个免费的层,所以您可以不花一分钱开发和演示。这些好处是以灵活性为代价的。App Engine标准只支持某些语言和库,不允许对磁盘或SSH进行写入。换句话说,环境是标准化的。

Answer: NodeJS Support on App Engine Standard

答:NodeJS支持App引擎标准

If you are interested in NodeJS support on App Engine Standard, please star this issue: https://issuetracker.google.com/issues/67711509.

如果您对应用程序引擎标准的NodeJS支持感兴趣,请关注以下问题:https://issuetracker.google.com/issues/67711509。

Google addresses features that get attention from the community (see here). The best way to give your attention to this feature, is to star it on the Google Issue tracker linked to above.

谷歌解决了引起社区关注的特性(参见这里)。要注意这个特性,最好的方法是在上面链接的谷歌问题跟踪器上显示它。

#9


1  

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

谷歌于2016年3月21日宣布了该节点。谷歌App Engine上的js正在进行beta测试:https://cloudplatform.googleblog.com/2016/03/node.js -on-Google- app-engine -goes-beta.html?

This was expected as Google also joined the Node.js Foundation and Google develops the V8 JavaScript engine which powers Chrome and Node.js: https://nodejs.org/en/blog/announcements/welcome-google/

这是预期的,因为谷歌也加入了节点。js Foundation和谷歌开发了V8 JavaScript引擎,支持Chrome和Node。js:https://nodejs.org/en/blog/announcements/welcome-google/

Google announced a partnership with NodeSource at the same time.

谷歌同时宣布与NodeSource合作。

#10


1  

Google has just announced support for Node.js on App Engine.

谷歌刚刚宣布支持Node。js App Engine。

为什么javascript节点。不是在谷歌应用程序引擎上 See: https://cloud.google.com/nodejs/

参见:https://cloud.google.com/nodejs/

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

这里有一个如何部署Node的示例。app Engine上的js应用。

#11


0  

Google is a software-conservative company. Programming a backend in JavaScript would be absolutely unimaginable for Google's managers. Creating infrastructure Google itself won't be using is not a good investment. Reference: Notes from the Mystery Machine Bus

谷歌是一家软件保守型公司。对谷歌的管理人员来说,用JavaScript编写后端是绝对不可想象的。创建基础设施谷歌本身不会使用,这不是一个好的投资。参考:神秘机器总线的记录。

#1


32  

As of June 2014, Google had a limited preview for custom languages on Google App Engine (which is different from Google Compute Engine).

到2014年6月,谷歌在谷歌应用引擎上对自定义语言进行了有限的预览(与谷歌计算引擎不同)。

Watch Building Node.js applications with App Engine and Custom Runtimes and check out https://cloud.google.com/appengine/docs/managed-vms/:

看建筑节点。使用App Engine和自定义运行时的js应用程序,请查看https://cloud.google.com/appengine/docs/managed-vms/:

App Engine now offers a second hosting option: Managed VMs. The Managed VM hosting environment lets you run App Engine applications on configurable Compute Engine Virtual Machines (VMs). You can also use Managed VMs to deploy user-configurable custom runtimes, such as for Node.js and other runtimes.

App Engine现在提供了第二个托管选项:托管vm。托管VM托管环境允许您在可配置的计算引擎虚拟机(VMs)上运行应用程序引擎应用程序。您还可以使用托管vm来部署用户可配置的自定义运行时,比如Node。js和其他运行时。

The procedure to get into the beta is:

进入测试的程序是:

Sign up and create a Managed VM project

Managed VMs are in Limited Preview, you must sign up for access to this feature, create a billing-enabled project, and tell us about your project so we can whitelist it to run in a Managed VM. Follow these steps:

受管理的VM在有限的预览中,您必须注册以访问这个特性,创建一个启用了billing的项目,并告诉我们您的项目,以便我们可以将其在受管理的VM中运行。遵循以下步骤:

  1. Sign up for access to Managed VMs.
  2. 注册访问托管vm。
  3. Join the app-engine-managed-vms Google Group to participate in discussions about Managed VMs.
  4. 加入app-engine- managedvms谷歌组,参与关于托管vm的讨论。
  5. Projects (or apps - they are the same thing) must be in a U.S. data center. If you're planning to use an existing project, skip to the next step. Otherwise, create a new app in a U.S. data center. Navigate to https://preview.appengine.google.com and create a new app.
  6. 项目(或应用程序——它们是一样的东西)必须在美国的数据中心。如果您计划使用一个现有的项目,请跳到下一个步骤。否则,在美国数据中心创建一个新的应用程序。导航到https://preview.appengine.google.com并创建一个新的应用程序。
  7. Enable billing for the project. Visit the page https://cloud.google.com/console/project/apps~, where is the ID of your project. Click on Settings in the left menu and then enable billing. If your app is billed under a Premier account, email us at app-engine-managed-vm-tt-id@google.com to have your new Cloud project billed under the same account.
  8. 支持项目的计费。访问页面https://cloud.google.com/console/project/apps~,你的项目的ID在哪里。单击左侧菜单中的设置,然后启用计费。如果你的应用是在一个主要账户下收费的,请发邮件到app-engine管理的vm-tt-id@google.com,让你的新云项目在同一个账户下收费。
  9. Send an email to app-engine-managed-vm-tt-id@google.com with the application ID in the subject line.
  10. 向app-engine管理的vm-tt-id@google.com发送电子邮件,标题行中包含应用程序ID。

When we receive your email, we’ll configure some resources behind the scenes and notify you via email when your project is ready to go. The email includes final instructions for setup. If you encounter an error while following these instructions, contact us at app-engine-managed-vm-tt-id@google.com.

当我们收到您的电子邮件时,我们将在后台配置一些资源,并在项目准备就绪时通过电子邮件通知您。这封电子邮件包含安装的最终说明。如果您在遵循这些说明时遇到错误,请通过app-engine-managed-vm-tt-id@google.com联系我们。

#2


40  

Node.js is maintained by Joyent, who is in a way a competitor of Google.

节点。js由Joyent维护,Joyent在某种程度上是谷歌的竞争对手。

Node.js has no link what so ever with Google but is in fact built on top of an open source project started by Google.

节点。js与谷歌没有任何联系,但实际上是建立在由谷歌启动的开源项目之上的。

Google might jumped into this business just like Azure did, but there are already so many PaaS doing it, it might not be worth it. I have never used GAE, but my understanding is that it is quite different that other PaaS and you have to use GAE libraries to make your code run.

谷歌可能会像Azure一样投入到这个业务中,但是已经有很多的PaaS做了,可能不值得。我从未使用过GAE,但我的理解是,与其他PaaS和您必须使用GAE库来运行代码是完全不同的。

Which, this is my personal feeling, is not really what the Node.js community is looking for. Node.js is used to quickly make a fast lightweight app, a big share for APIs for Phone apps for example.

这是我个人的感觉,并不是真正的节点。js社区正在寻找。节点。js被用来快速制作一个轻量级的应用程序,比如手机应用程序的api。

Nevertheless if you are looking for a PaaS for Node.js, the are quite a few out there:

然而,如果您正在寻找节点的PaaS。js,有很多

  • Joyent (nodejitsu)
  • Joyent(nodejitsu)
  • dotCloud which has WebSockets support.
  • dotCloud支持WebSockets。
  • Windows Azure
  • Windows Azure
  • Nodester (bought by App Fog recently)
  • Nodester(最近被应用Fog收购)
  • Any Cloud Foundry host should support Node.js too.
  • 任何云的铸造主机都应该支持节点。js。
  • and many more...
  • 和更多的……

Those are just some names off the top of my head. There quite a few but those are the major ones. Oh there is Heroku too, but they don't have support for WebSocket which is a bummer for any Socket.IO based app.

这些只是我脑海里的一些名字。有不少,但那些是主要的。哦,也有Heroku,但是他们不支持WebSocket,这对任何Socket来说都很糟糕。基于IO的应用。

#3


23  

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

您可以在谷歌计算引擎(基本上是一个虚拟计算机)上安装node。这里有一个链接:https://developers.google.com/datastore/docs/getstarted/start_nodejs/

Regards Lars

认为拉斯

#4


21  

after years of experiences in google appengine, i switch to other cloud services now.

在谷歌appengine工作多年之后,我现在转向其他云服务。

i think google appengine is actually an old fashion service in cloud computing industry. which is slow to new technology, difficult to deploy, time wasting to learn the apis and lacking of a lot of features you need in languages you use.

我认为谷歌应用程序引擎实际上是云计算行业的一种老式服务。这对新技术来说是缓慢的,很难部署,学习api是浪费时间,而且在使用的语言中缺少很多需要的特性。

regardless of google's large community, i would not suggest anyone to use google appengine.

不管谷歌的大社区是什么,我都不会建议任何人使用谷歌appengine。

[newer paas]

(更新的paas)

i strongly recommend you to use openshift, appfog, heroku .etc's new paas cloud computing technologies, which are far more extensible, less change needing, more migrable from one platform to another, more freely coding in the beauty of the natural lanuage and its standard libraries without ugly platform specific apis.

我强烈建议您使用openshift、appfog、heroku .etc的新paas云计算技术,这些技术具有更强的可扩展性、更少的更改需求、更易于从一个平台迁移到另一个平台、更*地在自然语言和其标准库的优美环境中编码,而没有难看的特定于平台的api。

[iaas]

(iaas)

if you want more control over the running os environment, you may give linode, digital ocean, amazon, google cloud engine, microsoft azure etc. iaas providers a try.

如果您希望对运行的操作系统环境有更多的控制,您可以尝试使用linode、digital ocean、amazon、谷歌云引擎、microsoft azure等iaas供应商。

#5


13  

Because App Engine is a platform-as-a-service, and in order to add a new language/stack to GAE, Google need to create mid-level libraries that interface with the plethora of App Engine's services.

因为App Engine是一种平台即服务,为了向GAE添加新的语言/堆栈,谷歌需要创建与大量应用引擎服务相连接的中间层库。

Moreover, all App Engine apps is sandboxed and has several functionalities restricted from inside their sandbox environment. This means that beside the need to create service libraries, Google also need to create a secured sandbox environment for any language/stack that they try to introduce into GAE.

此外,所有应用程序引擎应用程序都是沙箱型的,并且有几个功能限制在沙箱环境中。这意味着除了需要创建服务库之外,谷歌还需要为它们试图引入到GAE的任何语言/堆栈创建一个安全的沙箱环境。

I personally think the second reason is why Google does not introduce support for new language/stack as aggressive as Azure did. App Engine is, in a way, more 'managed' than Azure, and has a larger initial development cost for new language/stack.

我个人认为第二个原因是为什么谷歌没有像Azure那样引入对新语言/栈的支持。在某种程度上,应用程序引擎比Azure更“受管理”,新语言/栈的初始开发成本也更高。

#6


3  

It has been released as of March 2016.

该片已于2016年3月上映。

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

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

#7


3  

Node.js has recently enabled support for Google Cloud users. The main document pages are:

节点。js最近支持谷歌云用户。主要文件页为:

It seems to require at the moment a Compute Engine instance.

目前似乎需要一个计算引擎实例。

#8


3  

Background: App Engine Standard vs App Engine Flexible

背景:App引擎标准vs App引擎灵活

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

在这个话题上似乎有些困惑,因为有两个版本的App Engine: Standard和Flexible。App Engine Flexible支持NodeJS,但不支持App Engine标准。(有关差异的更完整的解释,请参见这里)。

App Engine Standard scales in seconds (as opposed to minutes for the Flexible environment), and has a free tier, so you can develop and demo without spending a dime. These benefits come at the cost of flexibility. App Engine Standard only supports certain languages and libraries, doesn't allow writing to disk nor SSH. In other words, the environment is standardized.

应用程序引擎标准以秒为单位伸缩(与灵活的环境不同),并且有一个免费的层,所以您可以不花一分钱开发和演示。这些好处是以灵活性为代价的。App Engine标准只支持某些语言和库,不允许对磁盘或SSH进行写入。换句话说,环境是标准化的。

Answer: NodeJS Support on App Engine Standard

答:NodeJS支持App引擎标准

If you are interested in NodeJS support on App Engine Standard, please star this issue: https://issuetracker.google.com/issues/67711509.

如果您对应用程序引擎标准的NodeJS支持感兴趣,请关注以下问题:https://issuetracker.google.com/issues/67711509。

Google addresses features that get attention from the community (see here). The best way to give your attention to this feature, is to star it on the Google Issue tracker linked to above.

谷歌解决了引起社区关注的特性(参见这里)。要注意这个特性,最好的方法是在上面链接的谷歌问题跟踪器上显示它。

#9


1  

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

谷歌于2016年3月21日宣布了该节点。谷歌App Engine上的js正在进行beta测试:https://cloudplatform.googleblog.com/2016/03/node.js -on-Google- app-engine -goes-beta.html?

This was expected as Google also joined the Node.js Foundation and Google develops the V8 JavaScript engine which powers Chrome and Node.js: https://nodejs.org/en/blog/announcements/welcome-google/

这是预期的,因为谷歌也加入了节点。js Foundation和谷歌开发了V8 JavaScript引擎,支持Chrome和Node。js:https://nodejs.org/en/blog/announcements/welcome-google/

Google announced a partnership with NodeSource at the same time.

谷歌同时宣布与NodeSource合作。

#10


1  

Google has just announced support for Node.js on App Engine.

谷歌刚刚宣布支持Node。js App Engine。

为什么javascript节点。不是在谷歌应用程序引擎上 See: https://cloud.google.com/nodejs/

参见:https://cloud.google.com/nodejs/

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

这里有一个如何部署Node的示例。app Engine上的js应用。

#11


0  

Google is a software-conservative company. Programming a backend in JavaScript would be absolutely unimaginable for Google's managers. Creating infrastructure Google itself won't be using is not a good investment. Reference: Notes from the Mystery Machine Bus

谷歌是一家软件保守型公司。对谷歌的管理人员来说,用JavaScript编写后端是绝对不可想象的。创建基础设施谷歌本身不会使用,这不是一个好的投资。参考:神秘机器总线的记录。