旨在轻松迁移到 Google App Engine
我很快就会开始设计一个 Web 应用程序,虽然我在 SQL 领域拥有丰富的经验,但我不知道这样做需要考虑什么,以便在不久的将来迁移到 GAE未来。
或者,我可以从一开始就为 GAE 设计应用程序,那么在这种情况下,我需要考虑哪些差异?换句话说,从过去的关系数据库来看,为 GAE 编写应用程序应该做什么和不应该做什么。
I am going to start designing a web app shortly, and while I have lots of experience doing it in the SQL world, I have no idea what I need to take into consideration for doing so with the goal of migrating to GAE in the very near future.
Alternatively, I could design the app for GAE from the start, and so in that case, what are the differences I need to take into consideration? In other words, what are the DOs and DONTs of writing your app for GAE, coming from a relational databases past.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
就在我的脑海中:
OFFSET(在 SELECT 中) - 所以实际上你获取了所有记录直到 offset- 正如 Nick Johnson 在评论之一中指出的,它不是客户端,所以现在,由于 1000 的 LIMIT 已经消失,它与 SQL 数据库类似。所有这些意味着您可能无法避免向用户暴露不一致的状态,并且几乎可以肯定您无法避免数据的不一致状态(例如,在手动 JOIN 数据更改期间,一半行已迁移,一半未迁移)
Just out of top of my head:
OFFSET (in SELECT) implemented on client side - so in fact you fetch all records up to offset- as pointed by Nick Johnson in one of the comments, it's not client side, so now, as LIMIT of 1000 is gone it's similar to SQL databases.All that means that you probably can't avoid exposing inconsistent state to user, and almost for sure you cannot avoid having inconsistent state of your data (e.g. half rows migrated and half not, during manual JOIN data changes etc)