Google App Engine, what do you think?

Portal Home > Knowledgebase > Articles Database > Google App Engine, what do you think?

Posted by dasPing, 08-07-2011, 03:43 PM
I am curious about people's experience with GAE as a backend of frontend.
Posted by oker, 08-07-2011, 05:57 PM
What do you mean by "backend of frontend"?
Posted by quantumphysics, 08-07-2011, 06:36 PM
probably means 'or'
Posted by dasPing, 08-08-2011, 01:35 AM
yes, sorry frontend (ie jsp,html,gwt) or backend (server.database)
Posted by fireboltz, 08-16-2011, 02:06 AM
I exactly want to know what does this mean . can anyone help me out regarding backend and frontend
Posted by ServerPronto, 08-16-2011, 11:53 AM
Difference between frontend, backend, and middleware in web development: http://stackoverflow.com/questions/6...eb-development
Posted by dasPing, 08-16-2011, 02:57 PM
The backend for google app engine would be the logic that writes, and reads into a database. Whilst the frontend is the presentation code. For google app engine that would normally be Google Webkit Ajax-Javascript or Java Servlet Pages.
Posted by Host1Plus, 08-16-2011, 04:35 PM
You see the front end of GAE. If you want to get into the backend, I guess you need to apply for a job at Google
Posted by vikramrandhawa, 08-17-2011, 05:43 AM
backend basically related to the database . Like Information displayed at front end.will come from the backend i.e database.
Posted by sodgnsiodg, 08-23-2011, 10:11 AM
frontend of backend?
Posted by Schmarvin, 08-23-2011, 10:55 AM
Apparently, you don't know how to read. READ THE POSTS AFTER IT! God I hate spam. I haven't been able to see much of the Engine being used. But, I wouldn't mind seeing just the backend capabilities of it.
Posted by sodgnsiodg, 08-23-2011, 11:11 AM
That was a joke take it easy
Posted by boushy, 08-24-2011, 11:18 PM
Frontend wil be the presentation layer that will be vicible to the end user. Backend will be the data processing engine that you write.
Posted by jjk2, 08-29-2011, 09:28 AM
is GAE cheaper than amazon?
Posted by tchen, 08-29-2011, 10:40 AM
Assuming we're not talking about the restrictive free tier, Instances will be billed at 0.08/hr or committed rate of 0.05/hr. Data storage be 0.24/GB. Bandwidth is 0.12/GB. Google App Engine for business also requires a $9 monthly fee on top of the usage. http://googleappengine.blogspot.com/...pp-engine.html So, it's generally close to EC2 small instances. That said, it hides a lot more of the redundancy infrastructure so you don't have to worry about individual servers, which should be worth some premium to you.
Posted by che09, 09-01-2011, 07:01 PM
Compared to other scalable hosting services, App Engine provides more infrastructure to make it easy to write scalable applications, but can only run a limited range of applications designed for that infrastructure.
Posted by klisja, 09-01-2011, 08:25 PM
A quick clarification from Google's FAQ:
Posted by tchen, 09-02-2011, 02:46 AM
Thanks for the update.
Posted by MetaCDN-JamesB, 09-06-2011, 02:23 AM
We use GAE extensively @ MetaCDN for our front-end/presentation layer. If you can shoehorn your app into the App Engine "model" then it can work and scale rather well. However, with the recent price increase (and move from CPU-hours to instance hours) there are now a lot of unhappy GAE developers. Many (us included) are seeing a 10x increase in cost.
Posted by vikramrandhawa, 09-07-2011, 05:08 AM
How we can explain the frontend of backend.. Because i think front end is just the Front or design view of the pages.. and Backend means where all whole website information store.
Posted by colosolutionz, 09-07-2011, 03:53 PM
Compared to EC2, I haven't heard an outages with GAE, whereas there have been several with EC2.
Posted by tchen, 09-07-2011, 07:24 PM
Just do a google search for "google app engine outage" and filter by date for the last year and you already get: Mar 8, 2011 July 14, 2011 August 18, 2011 Granted, GAE does distribute your code for you, so the outages tend to show up as blips in unavailability, much like AWS on a whole was still up and running despite certain people being knocked offline. http://www.zdnet.co.uk/news/web-apps...blip-40093421/ Like all things, GAE is still subject to the laws of scalability and have acted to remedy things like making available a separate reliable datastore, etc. Things both providers have been striving to fill in the gaps with. http://www.zdnet.co.uk/news/cloud/20...ages-40091338/
Posted by MetaCDN-JamesB, 09-27-2011, 11:30 PM
There has been plenty of GAE outages - just last week the login service was borked for 12 hours! This should improve shortly as GAE moves out of preview and there is a proper SLA.
Posted by Yash-JH, 09-28-2011, 02:28 AM
Google App Engine is PaaS, EC2 is an IaaS.. Apples vs Oranges... PaaS takes the pain out of scalable application hosting, and Google App Engine is definitely a great option for the stacks they support.
Posted by tchen, 09-28-2011, 12:38 PM
Don't get me wrong. GAE can be good if you don't want to manage the stacks yourself. Much like AWS has its series of (PaaS) managed databases, memcache, etc. But don't kid yourself in thinking such services are magically immune to service degradations or outages. They will happen, and luckily they tend to be worked on by very experienced individuals. In a lot of cases, this is much better than rolling it yourself. Its all good as long as you understand what you have given up for that ease-of-use and hassle free setup.
Posted by MetaCDN-JamesB, 09-29-2011, 09:00 PM
Front-end instances are usually dynamic, and often short lived instances that serve your public facing pages. They have certain limits associated with them also - interactive requests cannot take more than 30 seconds, cron/worker type background requests can take up to 10 minutes to execute. Back-end instances are usually private, and can use larger instance sizes (containing more CPU and memory). The instances are more durable and are individually addressable. They also have no limit on how long a task can execute for. I recommend reading the GAE docs for more info.

Add to Favourites Print this Article