Comments on: Google App Engine: The good, the bad, and the ugly?

By: doug

doug — Wed, 20 May 2009 22:44:42 +0000

@magallanes

I suspect there is a language barrier here. What exactly do you mean by ‘webservice’? The point of GAE is to have you deploy your web APP. It is not about you providing web hosting to others. With that said you can write an ‘APP’ which people whom are logged in can create a web page for them selves. People have done that. But that is a far cry from web hosting. If you are talking about systems where you write something which provides and API (REST or otherwise) for other sites to use… that is the #1 use of GAE. There is no documentation specificly for that because the GAE documentation IS documentation for that type of web service.

By: magallanes

magallanes — Wed, 20 May 2009 17:34:01 +0000

Hi there:

May be this reply is a bit later but… anyways.

Google App Engine now support Java (yay?) but currently is in beta so we are still stick on Python.
I must admit, i don’t have any experience with python but i still manage to do some stuffs. But i tried to do some worthy, a single and common task :a webservice in phyton.. And SURPRISE!!… there are few information about GAE and webservice. How strange?. because the “raison d’etre” of GAE is to create service. In any case, is not native, neither easy to create a single webservice. weird.

By: Google App Engine limitations, and how to get around them | Digitalistic - Mashup or die trying

Tue, 16 Sep 2008 13:40:57 +0000

[...] limitations There are more limitations, read Google App Engine: The good, the bad, and the ugly? for a more detailed list. Just keep in mind that some of the limitations mentioned in that post [...]

By: systemsplanet.com

systemsplanet.com — Mon, 14 Jul 2008 02:35:48 +0000

no https is a killer for me.
Any apps that handle sensitive info (like
personal info, ssn, credit card info, etc).

By: William Vambenepe's blog

William Vambenepe's blog — Sat, 31 May 2008 22:51:55 +0000

Google App Engine: less is more…

“If you have a stove, a saucepan and a bottle of cold water, how can you make boiling water?”
If you ask this question to a mathematician, they’ll think about it a while, and finally tell you to pour the water in the saucepan, light u…

By: Development, Eclipse, Google, Web and other forecasts « Mantrid’s Weblog

Fri, 25 Apr 2008 10:45:23 +0000

[...] look at Google App Engine. Emphasizes its distinctness from typical development enviroment. And another one worth [...]

By: Gary

Gary — Tue, 22 Apr 2008 01:41:32 +0000

Great post. I agree on your points on PHP/Ruby/RoR. I don’t know Python, so this is as good a reason as any to start learning.

By: friarminor

friarminor — Mon, 14 Apr 2008 07:19:38 +0000

For Google, it sure is a big start. But I will be extremely surprised if they don’t venture supporting Ruby on Rails and trample over upstarts such as Morph eXchange in that category.

But on the bright side, platform and on-demand deployments are really interesting..

Best.
alain

By: Alex Martelli

Alex Martelli — Mon, 14 Apr 2008 05:31:41 +0000

Excellent summary Doug — I wish more than 1% of the posters had as much insight into the technical AND (indirectly) business issues of App Engine as you do…!-)

Alex

By: sean

sean — Mon, 14 Apr 2008 04:55:32 +0000

google offers a platform that everybody could use, it saves much pain of setting up the environment if you just want to make a simple application.
not flexible enough for big companys, but it’s good enough for individuals.