我正在尝试创建一个 MVP（最小可行产品）。 Google App Engine 是一个很好用的框架吗？
我正在尝试创建一个 MVP（最小可行产品）。Google App Engine 是一个很好用的框架吗？
我的项目相当于一个垂直问答网站，与 Quora 没什么不同。就像在 Quora 上一样，我希望用户能够关注其他用户并关注主题。所有问题都将标记为 15 个主题之一。
如果 Google App Engine 不是此类项目的良好框架，您有何建议？我还考虑过 Django 和 Amazon Web Services。
值得注意的是，我的编程经验很少（主要是 Java 和 MySQL）。然而，我愿意学习任何最有用的语言。
I am trying to create a MVP (minimal viable product).. Is the Google App Engine a good framework to use?
My project amounts to a vertical Q and A site not unlike Quora. Just as on Quora, I want users to be able to follow other users and follow topics. All questions will be tagged in one of 15 topics.
If Google App Engine is not a good framework for this sort of project, what would you suggest? I have also considered Django and Amazon Web Services.
It is important to note that I have minimal programming experience (primarily in Java and MySQL). However, I am willing to learn whatever language would be most useful.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
问答网站本质上并不适合 App Engine - 事实上，我在 2009 年阿姆斯特丹 Stack Overflow 开发日上的演讲是“如何在一小时内在 App Engine 上编写 Stack Overflow 克隆”。
不过，您似乎混淆了堆栈的不同层：Django 是一个框架； App Engine 是一个平台，AWS 是基础设施。您可以在 App Engine 上使用 Django。
There's nothing about a Q&A site that's intrinsically poorly suited to App Engine - in fact, my talk at the Stack Overflow Dev Day 2009 in Amsterdam was "How to write a Stack Overflow Clone on App Engine in under an hour".
You appear to be confusing different layers of the stack, though: Django is a framework; App Engine is a platform, and AWS is infrastructure. You can use Django on App Engine.
GAE 有一些限制。这完全取决于您产品的具体情况。例如，GAE 对您可以与第 3 方保持连接的时间设置严格限制服务器打开。这是你需要做的事情吗？
因此，我建议您阅读 GAE 的各种限制，并根据您的初始设计确定它们是否对您来说是个问题。
另一个需要考虑的点是搭配。如果您的最小产品取得了成功，您很可能会想要继续开发它，而不是从头开始重写。如果您依赖 GAE 的各种专有存储、bg 工作人员等，那么切换起来就会困难得多。顺便说一句，这是我为自己的应用程序选择退出 GAE 的主要原因。如今，在某些云提供商处获得自己的托管虚拟服务器已经足够便宜，而且您当然可以使用 Django，因此 GAW 可能不会为您带来太多附加价值。
GAE has some limitations. It all depends on the specifics of your product. For example, GAE puts strict limits on how long you can keep connections to 3rd party servers open. Is this something you'd need to do?
So, I would advise you to read up on GAE's various limitations and find out if they're a problem for you or not, based on your initial design.
Another point to consider is the tie-in. If your minimal product is successful, most likely you'll want to continue developing it, instead of rewriting from scratch. If you rely on GAE's various proprietary storage, bg workers, etc. it's going to be that much harder to switch. This, incidentally, is the main reason I opted out of GAE for my own app. It's cheap enough these days to get your own hosted virtual server at some cloud provider and you can use Django anyway, of course, so GAW might not have that much added value for you.