为的AppEngine网站架构指导？ [英] Architecture guidance for appengine websites?

问题描述

我创建使用PHP难以维护的网站，因为它是那么容易做的事情快速和肮脏。我不想做谷歌的AppEngine上使用Python / Django的同样的事情。

I've created unmaintainable websites using PHP because it was so easy to do things quick and dirty. I don't want to do the same thing with Python/Django on Google's appengine.

有用于创建使用Django和网站的AppEngine任何好的体系结构参考？ （例如，在把业务逻辑在哪里把数据访问逻辑，如何分离干净的意见，如何做单元测试，等等。）

Is there any good architecture references for creating websites using Django and appengine? (E.g. where to put business logic, where to put data access logic, how to cleanly separate the views, how to do unit testing, etc.)

推荐答案

请记住Django的版本包括App Engine是不完整的，需要更新，如果你想所有的MVC功能。

Keep in mind the version of Django included with App Engine is incomplete and needs to be updated if you want all the MVC features.

我自己的经验建立一些应用程序，我建议只是坚持内置的web应用框架，如果预计编写小于2或3000线code后。这是管理的，恕我直言，你会不会从去Django的收获很多，但是你的源代码树会有很多混乱与所有的Django框架文件。

After my own experience building a few apps I recommend just sticking to the built-in webapp framework if you anticipate writing less than 2 or 3000 lines of code. It is manageable and imho you won't gain much from going to Django, but your source tree will be a lot messier with all the Django framework files.

这篇关于为的AppEngine网站架构指导？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！