从Google App Engine迁移有多困难? [英] How difficult is it to migrate away from Google App Engine?

查看:184
本文介绍了从Google App Engine迁移有多困难?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在考虑制作一个(最初)小型Web应用程序,它最终有可能增长。所有被视为Google App Engine的东西看起来都是非常有吸引力的选择。比如说,用户群和复杂性都在增长,出于某种原因,我需要离开GAE。迁移有多难?



1)GAE是否提供导出数据库的方式?它是什么格式? 2)在哪些领域(例如数据库访问,其他领域)我将不得不使用GAE API ?即哪些部分的实现必须被抽象出来/接口?

编辑:3)或者,它甚至值得抽象出GAE API?

解决方案

对于问题1:我不知道GAE是否特别支持数据库的导出,但您始终可以自己推出, 最坏的情况。如果您处于需要的位置,您可能也有资源来完成这项工作。



对于问题2:您可以并且应该始终封装无论如何这些外部依赖关系。它们是否提供接口并不重要。与这些界面的耦合应该保持在绝对最低限度。



对于问题3:这个问题并不是非常清晰,所以我无法回答。


I am thinking of making an (initially) small Web Application, which would eventually have a potential to grow. All things considered Google App Engine seems like a very attractive option. Say, user base and complexity grows and for one or other reason I needed to leave GAE behind. How difficult would it be to migrate away?

1) Does GAE provide a way to export the database? What format would it be? Would it be difficult to put it under MySQL (or similar)?

2) In which areas (ex. database access, others?) would I have to use GAE API? I.e. which parts of implementation would have to be abstracted away / interfaced?

Edit: 3) Alternatively, is it even worth to abstract away GAE API?

解决方案

For question #1: I don't know if GAE specifically supports exports of a database but you can always roll your own, worst case scenario. If you are in a position where you need to, you'll probably have the resources to do it, too.

For question #2: You can and should always encapsulate those kinds of outside dependencies anyway. It doesn't matter whether or not they provide interfaces. Coupling to those interfaces should be kept to an absolute minimum.

For question #3: This question is not really super-clear so I cannot answer it.

这篇关于从Google App Engine迁移有多困难?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆