I want to deploy and app using compute engine as my company does not provide access to app engine yet. Is there a way to deploy the same app using compute engine rather than app engine on google cloud. I have searched multiple forum but unable to find relevant answers.
Any help would be much appreciated.
With python3, I recommend you to write a Flask web application. Your web application will be similar on App Engine and on your compute.
However, you have several things to perform at the infrastructure level. I recommend you to have a look to managed Instances group with auto scaling and health check and Global load balancer.
Note: Because, it's not serverless, you have to pay at least 1 instance even if there isn't traffic on your app
Alternatively, you can have a look to GKE (easier VM management and scaling) and Cloud Run.
Overview of problem. Site was running on a Free version of Google Apps for over a year as a simple web page. We started developing it we deleted the old Google Apps and and migrated it to our primary App Engine account to avoid billing issues of two+ accounts. We couldn't get App Engine to recognize the Custom Domain even though it was in the Domains tab of our Google Apps Account. In searching I found Google limits using domains on App Engine (http://support.google.com/a/bin/answer.py?hl=en&answer=182081 scroll down to App Engine) I had to recreate a separate Google Apps account to verify ownership of the domain. Site is up and operational now outside of SSL. The issue is that when I go to https://admin.google.com/CPanelHome#DomainSettings/subtab=domains and type the app id to enable SSL on the domain Apps account it routes me to create an App Engine app instead of to billing. Because the app is running on the primary App Engine account not the Domain account.
It seems someone must have ran across this and solved it. How do I enable my primary Google Apps account to verify ownership of the domains and allow App Engine to use it? I have a lot of domains that will be hosted on App Engine and a lot of integration between the sites that would really need to be all under a single account to facilitate.
I noticed in searching that Google is offering a free year of Google Apps for customers using App Engine to host a application. Is Google expecting every domain to have a full Google Apps account and host on separate App Engine accounts? If so that would really limit our ability to use App Engine.
After waiting for three days for an answer I am moving on. I believe I tried every way imaginable to accomplish getting multiple domains on a primary Google Apps account to be verified and have SSL enabled. I went so far as to try it with a domain that has never had any Google services. Just in case there were some settings that were causing issues from left over configuration.
So the resolution of this at this time is Google expects you to have a full Google Apps account per domain to enable SSL, or Google App Engine on it. I believe they will be removing the Free Google App Account in the near future. This effectively means that hosting on App Engine will get expensive as a Google App Account is $50/year, and if you use a CloudSQL instance it will be at minimum $9/mo. That is on top of the bandwidth and usage fees.
I have already deactivated billing and disabled the apps on those accounts and have moved them over to a VPS. This is the third year I have spent a lot of time trying to get basic sites using SSL established on Google. While this year it is possible to do it, in the end you pay an arm and a leg for it.
I love Google and really want App Engine to be viable. But I just don't think they will pull it together. All my friends have went with Azure, RackSpace, and the granddaddy Amazon. It really makes me sad that Google is so far from viable and even worse that Azure just works.
If anyone at Google wishes to contact me feel free to do so. If there is something I missed feel free to open this and give directions on how to host multiple domains on a single App Engine / Apps account with SSL. I would greatly appreciate it.
Google created the V8 JavaScript engine: V8 compiles JavaScript source code directly into machine code when it is first executed.
Node.js is built on V8 - why is Google not offering any Node.js servers like Microsoft Azure?
Google App Engine would be a natural place to put Node.js.
Do you know why Google is not doing just that?
Node.js is maintained by Joyent, who is in a way a competitor of Google.
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.
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.
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.
Nevertheless if you are looking for a PaaS for Node.js, the are quite a few out there:
Joyent (nodejitsu)
dotCloud which has WebSockets support.
Windows Azure
Nodester (bought by App Fog recently)
Any Cloud Foundry host should support Node.js too.
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.
As of June 2014, Google had a limited preview for custom languages on Google App Engine (which is different from Google Compute Engine).
Watch Building Node.js applications with App Engine and Custom Runtimes and check out 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.
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:
Sign up for access to Managed VMs.
Join the app-engine-managed-vms Google Group to participate in discussions about Managed VMs.
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.
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.
Send an email to app-engine-managed-vm-tt-id#google.com with the application ID in the subject line.
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.
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/
Regards
Lars
after years of experiences in google appengine, i switch to other cloud services now.
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.
regardless of google's large community, i would not suggest anyone to use google appengine.
[newer 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.
[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.
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.
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.
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.
It has been released as of March 2016.
https://cloudplatform.googleblog.com/2016/03/Node.js-on-Google-App-Engine-goes-beta.html
Node.js has recently enabled support for Google Cloud users. The main document pages are:
Node.js on Google Cloud Platform
Google Cloud Datastore — Google Developers
It seems to require at the moment a Compute Engine instance.
Background: App Engine Standard vs App Engine Flexible
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 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.
Answer: NodeJS Support on App Engine Standard
If you are interested in NodeJS support on App Engine Standard, please star this issue: 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.
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
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/
Google announced a partnership with NodeSource at the same time.
Google has just announced support for Node.js on App Engine.
See: https://cloud.google.com/nodejs/
Here's an example of how to deploy Node.js app on App Engine.
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
(Jun 2021) This question is almost a decade old, and many things have changed since the OP. TL;DR: JavaScript and/or Node.js are supported in 6 different serverless compute platforms from Google: 4 on GCP and one each from Google Workspace and Firebase plus release dates:
Google App Engine - Standard (Jun 2018) - announcement, docs (Node.js 10, 12, 14; 8 is deprecated)
Google App Engine - Flexible (Mar 2016) - announcement (general release), docs (Most Node.js versions)
Google Cloud Functions (Mar 2017) - announcement (general release), docs (Node.js 10, 12, 14; 8 is deprecated)
Cloud Functions for Firebase (Mar 2017) - announcement, docs (same versions as Google Cloud Functions)
Google Cloud Run (Apr 2019) - announcement (general release), docs (Any Node.js version you can put in a container)
Google Apps Script (Aug 2009) - announcement, docs (JS-only, not Node; Rhino ES3/ES5 + extensions originally; now v8 & ES6+ [Mar 2020])
Also see Google Cloud's overall support of/for Node.js.
Can i develop multiple applications on Google app engine or Amazon AWS??
Does it violate any of the Google app engine and Amazon AWS rules??
Plz advice me on this topic
Yes, you can have multiple applications. But for Google there is a limit of 10 applications per developer. In Amazon there is no limit (other than capacity) of number of servers you can buy and no one really asks how many applications are there, unless you perform illegal actions with it (eg. spam).
on Google AppEngine you can't use multiple applications as a way to avoid fees for you application.
So your applications should be different, and you can't deploy many instances of the same application so you get more 'free' allocation.
From the GAE terms of service
4.4. You may not develop multiple Applications to simulate or act as a single Application or otherwise access the Service in a manner
intended to avoid incurring fees.
I'm finding alternatives for Google App Engine for startup. The preconfigured service hosting include security, networking, scaling, database, backup, application, maturity and etc.. Because we have no experts on each parts. It's too hard operating whole service stack properly for only one application programmer.
What other services can I consider for this?
The term you want to search for is PaaS or Platform-as-a-Service. I do not claim to be an expert in this nacent field, however my basic understanding of the key players other than Google App Engine are:
Amazon AWS - My understanding is that Amazon's Web Services gives you bare-bones OS installs that you can completely own. While this allows for more configuration than App Engine, this also means you are on the hook for patching security holes and what not. (Right?)
Heroku - App Engine type functionality, except for Ruby
AppHarbor - App Engine type functionality, except for .NET
Microsoft Azure - Amazon AWS type functionality, except for Windows/The Microsoft stack.
The CloudCamp awards 2011 serves as a nice list of PaaS services