移动到一个多层次的体系结构德尔福建议 [英] Advice on moving to a multi tier Delphi architecture

问题描述

我们有一个比较大的应用程序，强烈扎成火鸟（存储过程，视图等）。我们现在收到了很多要求，以支持更多的数据库，我们也想了很多的功能，从客户端转移到服务器。

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）三层架构。我们已经看了2009年的DataSnap和的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).

这篇关于移动到一个多层次的体系结构德尔福建议的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！