I'm developing a web app on Google App Engine, for which I recently decided that it requires a high performance inbound email processing functionality. GAE's functionalities for incoming email are rather limited, however CloudMailIn on Heroku seems to be able to do everything that I want (https://addons.heroku.com/cloudmailin)
Would you consider it a wise decision to run the website, user accounts, and databses on GAE, and run CloudMailIn separately with e.g. an API connection to write to the datastore on GAE? So far I have built all my web apps on GAE, so I prefer to stick with what I know. However if this is likely to bite me once I scale, then of course I will move everything to Heroku. Does anybody have experience with this?
Thanks to answers from Peter and Steve I now understand that both Sendgrid and CloudMailIn can be controlled through a simple webhook, so no need to include Heroku here. FYI I ended up using MailGun Routes because their features had a better fit with my requirements.
Related
I have a relatively small Java app, which I'd like to move over to the Google App Engine. It runs in the console, with no user input needed after the initial startup. I researched a bit on how to deploy it, but all tutorials seem to focus on Java web apps, when I don't really need that. Is it possible to deploy my app if it's not a web app?
App Engine is probably the wrong GCP platform for you - you'd probably be better served just deploying your jar directly onto a Google Compute Engine node. GAE is pretty explicitly oriented around web applications and you'd need to do a bunch of configuration in order to have it work for your use case.
Does your non-web Java app handle web requests? If not, it seems difficult to imagine that you would be able to reach your deployed app and use it for any purpose, once deployed. Your Java app should be able to handle requests, to make deployment worthwhile, and the deployed app useful.
You may find out about how your app should handle requests by reading the How Requests are Handled documentation page.
I want to be able to host my website on google servers, i would like to design the website using react along with node js in the backend, from my current research it seems that google app engine is the way to go.
Am i on the right path or should i be looking at another avenue.I don't expect the site to intake a lot of traffic so a low cost plan would be ideal, a free plan would be amazing if possible if possible.
I also read that google dns could be used for a website which seems pretty convenient, how exactly do i go about this?
Your on the right path. Goole app engine flexible environment is the ideal choice for you. Since you want your backend to run in Nodejs it's very simple to run Nodejs in Google app engine. Google also give you free $300 for the free trial and you can use it for 12 months.
Read more about the pricing in here
Read more about Nodejs in Google app engine flexible here
Im starting a new application with AppEngine and I need a REST Service.
I was looking at Endpoints and I think they are exactly what I need.
I also read Google don't recommend to use Endpoints in production but my app first version is not going out until April approximately.
How mature do you think App engine Endpoints are?
Do you recommend to use them or should I find another REST framework.
If so, Are there any other REST framework similar to App Engine Endpoints?
or
Which one do you recommend, Restlet? or use it with Spring MVC?
Thanks
I'm a bit biased (being a Googler and member of the App Engine team), but I think Endpoints is worth a try. With regards to the general disclaimer on using Endpoints in production, we have allowed some developers to launch in production as long as they have spoken to us first.
I provided another answer to a related question on RESTful development here. The developer tried Endpoints and decided to use it over other options.
which is the best front-end solution for a GAE app. developed in Go?
best:=
the question is about choosing a solution that merges well with the GAE, as an example if I use GAE in Java I would pick up GWT, and I want to know how other people are using the GAE with Go;
why this question:=
the reason I'm asking this is that I want to understand if, today, there is an advisable path to follow in designing a web application that uses GAE with go when I have to choose something for the front-end ..and I'm trying to figure it out before digging into a useless 'reinventing the wheel coding mode'.
You can take a look at Gorilla web toolkit, is has been designed with App Engine in mind.
I have my website currently hosted on paid server, but i want to transfer it on GAE.
How can i do it? Can anyone please help me in this case.I'd appreciate your help.
Thanks:)
1) First you will have to adapt your website to the GAE framework (python with django or the new Java environment). You can test your work by downloading the SDK of GAE which offer a local server.
2) Then create an account on appengine.google.com and upload your application on something.appspot.com, test it.
3) If you have a domain name, create a google apps account on this domain, and finally bind this domain with your GAE website. Here is the Google doc.
If it is just a static website which does not need server side scripts or a database, then you might want to look into Google Sites instead of Appengine. You can find out more about Sites here: http://www.google.com/sites/help/intl/en/overview.html
If you do have some server side logic going on, you will need to convert it to either python or java and convert your relational database to Google's Data API which does not support the SQL your current database uses. You can read more about the APIs and what is supported with the Data API and tutorials at: http://code.google.com/appengine/
In response to sanorita's comment "Actually, it's generated html and not plain html. and google appengine is for static data... right?":
AppEngine can host static data, but that is far from its intent.
The purpose of AppEngine is to allow developers to easily deploy their dynamic applications on Google's infrastructure. In the end, assuming you have programmed your app in effective ways to handle scaling (basically just noting that writes to the database are expensive, and contention is the root of all evil) you can handle nearly any amount of traffic.