关于迁移到多层 Delphi 架构的建议 [英] Advice on moving to a multi tier Delphi architecture

问题描述

我们有一个与 Firebird 紧密相关的相对较大的应用程序(存储过程、视图等).我们现在收到了很多支持其他数据库的请求，我们还希望将很多功能从客户端转移到服务器.

We have a relatively large application that is strongly tied into Firebird (stored procedures, views etc). We are now getting a lot of requests to support additional databases and we would also like to move a lot of the functionality from the client to the server.

现在似乎是转向 3(4) 层架构的好时机.我们已经看过 DataSnap 2009 和 RemObjects SDK/DataAbstract.两者似乎都可以胜任，但是我们应该注意哪些优点/缺点?你有什么其他的框架可以推荐吗?

Now seems like a good time to move to a 3(4) tier architecture. We have already looked at DataSnap 2009 and RemObjects SDK/DataAbstract. Both seem like they would do the job, but are there any advantages/disadvantages we should look out for? Are there any other frameworks that you could recommend?

干杯，保罗

推荐答案

在迁移到多层应用程序的过程中，您可以考虑在层之间使用传输协议，该协议与语言/技术无关(如 Web 服务，(我认为塔 remobjects 支持))).

In the process of moving to a multitier application you could consider using a transport protocol between the layers, which is language/technology independent (like webservices, (i think tha remobjects supports that)).

这可以使以后重新实现层更简单(就像您以后必须在浏览器/java/silverlight 中制作另一个版本的客户端应用程序一样).

This could make a reimplementation of a layer simpler later (like if you later have to make a another version of the client-application in a browser/java/silverlight).

这篇关于关于迁移到多层 Delphi 架构的建议的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！