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

问题描述

我正在考虑制作一个(最初的)小型 Web 应用程序，它最终会有增长的潜力.所有被认为是 Google App Engine 的东西似乎都是一个非常有吸引力的选择.比如说，用户群和复杂性在增长，出于某种原因，我需要将 GAE 抛在脑后.迁移出去有多难?

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) GAE 是否提供导出数据库的方法?它会是什么格式?放在MySQL(或类似的)下会不会很困难?

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) 在哪些领域(例如数据库访问，其他?)我必须使用 GAE API?IE.实现的哪些部分必须被抽象掉/接口?

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?

3) 或者，是否值得抽象出 GAE API?

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

推荐答案

对于问题 #1:我不知道 GAE 是否专门支持数据库导出，但您始终可以推出自己的最坏情况.如果您处于需要的位置，您可能也有资源去做.

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.

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

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.

对于问题 3:这个问题不是很清楚，所以我无法回答.

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

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