有关使用Google App Engine的反馈？ [英] Feedback on using Google App Engine?

问题描述

想要做一个非常小，快速的肮脏的侧面项目。我喜欢Google App Engine在Python中运行，Django内置了这个事实 - 给我一个借口来尝试这个平台...但我的问题是这样的：

任何其他成功/失败的笔记将会很棒。

解决方案

我为我的小地震手表应用程序尝试了应用程序引擎
http://quakewatch.appspot.com/

我的目的是看应用程序引擎的功能，所以这里是要点：

1. 它不会默认使用django，它有自己的Web框架是pythonic具有URL调度程序，如django，它使用django模板
   所以如果你有django exp。你会发现它很容易使用
   
   
   
   
   • 但是你可以使用任何纯python框架和django可以轻松添加看到
     http://code.google.com/appengine/articles/django.html
     google- app-engine-django（ http://code.google.com/p/ google-app-engine-django / ）项目很好，几乎就像在django项目上工作
   
   


2. 你可以在服务器上不执行任何长时间运行的进程，你所做的是回复请求，应该是快速的，否则appengine会杀死它
   所以如果你的应用需要很多后端处理appengine不是最好的方式
   否则您将不得不在自己的服务器上进行处理


3. 我的quakewatch应用程序具有订阅功能，这意味着我必须发送最新的地震，但是我无法运行背景过程在ap p引擎监控新的地震
   解决方案是使用第三方服务，如pingablity.com，可以连接到您的一个页面，哪个执行订阅电子邮件
   ，但这里也将必须照顾你不会在这里花费太多时间
   或将任务分解成几件


4. 它提供了像Django一样的建模功能，但后端是完全不同的，但是对于一个新的项目，这不应该是重要的

但总体来说，我认为创建不需要大量后台处理的应用程序是非常好的。

编辑：
现在任务队列可用于运行批处理或计划任务

编辑：
在GAE上工作/创建一个真正的应用程序一年后，现在我的观点是除非您正在制作需要扩展到百万和百万用户的应用程序，否则不要使用GAE。在GAE中维护和执行微不足道的任务由于分布式性质而令人头痛，为避免最后期限超出错误，计数实体或复杂查询需要复杂代码，因此小型复杂应用程序应该遵守LAMP。

编辑：
模型应该是考虑到您以后要拥有的所有交易而特别设计的，因为仅在相同实体组中的实体可以在事务中使用，并且使更新两个不同组的过程一场恶梦，例如在交易中将钱从用户1转移到用户2是不可能的，除非他们在同一个实体组，但使他们相同的实体组可能不是最好的频繁更新目的....
读取这个 http://blog.notdot.net/2009/9/Distributed-Transactions-on-App-Engine

Looking to do a very small, quick 'n dirty side project. I like the fact that the Google App Engine is running on Python with Django built right in - gives me an excuse to try that platform... but my question is this:

Has anyone made use of the app engine for anything other than a toy problem? I see some good example apps out there, so I would assume this is good enough for the real deal, but wanted to get some feedback.

Any other success/failure notes would be great.

解决方案

I have tried app engine for my small quake watch application http://quakewatch.appspot.com/

My purpose was to see the capabilities of app engine, so here are the main points:

1. it doesn't come by default with django, it has its own web framework which is pythonic has URL dispatcher like django and it uses django templates So if you have django exp. you will find it easy to use
   • But you can use any pure python framework and django can be easily added see http://code.google.com/appengine/articles/django.html google-app-engine-django (http://code.google.com/p/google-app-engine-django/) project is excellent and works almost like working on a django project
2. You can not execute any long running process on server, what you do is reply to request and which should be quick otherwise appengine will kill it So if your app needs lots of backend processing appengine is not the best way otherwise you will have to do processing on a server of your own
3. My quakewatch app has a subscription feature, it means I had to email latest quakes as they happend, but I can not run a background process in app engine to monitor new quakes solution here is to use a third part service like pingablity.com which can connect to one of your page and which executes the subscription emailer but here also you will have to take care that you don't spend much time here or break task into several pieces
4. It provides Django like modeling capabilities but backend is totally different but for a new project it should not matter.

But overall I think it is excellent for creating apps which do not need lot of background processing.

Edit: Now task queues can be used for running batch processing or scheduled tasks

Edit: after working/creating a real application on GAE for a year, now my opnion is that unless you are making a application which needs to scale to million and million of users, don't use GAE. Maintaining and doing trivial tasks in GAE is a headache due to distributed nature, to avoid deadline exceeded errors, count entities or do complex queries requires complex code, so small complex application should stick to LAMP.

Edit: Models should be specially designed considering all the transactions you wish to have in future, because entities only in same entity group can be used in a transaction and it makes the process of updating two different groups a nightmare e.g. transfer money from user1 to user2 in transaction is impossible unless they are in same entity group, but making them same entity group may not be best for frequent update purposes.... read this http://blog.notdot.net/2009/9/Distributed-Transactions-on-App-Engine

这篇关于有关使用Google App Engine的反馈？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！