Google 应用引擎：个人经历？
我正在考虑在 Google App Engine 上制作一个应用程序，以帮助现有的不太大（1000 人）的社区在现有项目上进行一些特定领域的协作。在一个项目上有几个人一起工作，大部分时间都是在讨论事情。应用程序应该与可以托管在某处的“后端”通信，没有问题。
但我并不是在寻找另一个“利弊”讨论（例如，您可以在这里阅读：Google App Engine 的优点和缺点），但我更想听听其他人在类似情况下的经历。
有个人经验愿意分享吗？有想法吗？
I'm considering making an app on Google App Engine, to help an existing not-so-large (1000s) community with some field specific collaboration on existing projects. On single project work several people, mostly discussing things. App should communicate with "back-end" which can be hosted somewhere no problem.
But I'm not looking for another "pros and cons" discussion (for example you can read such here: Pros & Cons of Google App Engine ) but rather I'd like to hear about other people experiences in similar situations.
Any personal experiences willing to share? Ideas?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
App Engine 提供了出色的 API 来执行身份验证等常见任务，您几乎无需付出任何努力。
有些人在开始使用 App Engine 时还没有准备好应对一些独特的限制，例如 30 秒的请求超时或非关系数据存储，但一旦习惯了这些限制，解决这些问题并不困难，它们使您的应用程序尽可能快速且可扩展，即使在免费配额内也是如此。
还有很多很棒的文档，我建议您尽可能多地观看 Google I/O 您可以找到有关 App Engine 的讨论，它们都非常有用。
App Engine provides great APIs to perform common tasks like authentication with almost no effort on your end.
There are some unique limitations that some people aren't ready for when they start using App Engine, such as the 30s request timeout, or the non-relational datastore, but they're not difficult to work around once you're used to them, and they make your app as fast and scalable as possible, even within the free quota.
There's a lot of great docs, too, and I recommend watching as many Google I/O talks on App Engine as you can find, they're all really informative.
我想说，如果您不介意社区驱动的支持，GAE/Python 是一个令人愉快的开发平台。虽然我个人使用 tracko 的经历相当艰难，但这主要是因为我试图将数百万个请求放入免费中配额。
请注意重要问题，例如 HTTPS 支持以及模块所需的 Python 版本。检查是否有任何问题对您来说是个大问题。与往常一样，建议开发一个小项目来感受该平台。
I would say, GAE/Python is a pleasant platform to develop for, if you don't mind community-driven kind of support. Although my personal experience with tracko was quite rough, it was mostly because I tried to fit millions of requests into free quota.
Watch out for important issues, for example, HTTPS support and what Python version your modules require. Check if any of issues is a showstopper for you. As usual, it is recommended to develop a small project to get the feel of the platform.