2级和N级

问题描述：

嗨

我在这里寻找一些建议。我们正在使用VB.NET和ASP.NET Web Services创建分布式应用程序
（3层）。该架构遵循3层架构的b / b
。现在，我们的一个客户不想要

3层模型。他们希望应用程序只是一个客户端 - 服务器模型。我建议客户加入我们的3层

架构。

我的问题是的，如果我必须为这个

客户端制作客户端 - 服务器模型，那么最好的方法是什么。我试图避免使用两种不同的
解决方案 - 一种基于n层，另一种基于客户端 - 服务器模型。

所有建议都将受到高度赞赏。

谢谢

Raju ...

Hi

I am looking for some suggestions here. We are creating a distributed app
(3-tier) using VB.NET and ASP.NET Web Services. The architecture follows
that of a 3-Tier architecture. Now, one of our clients do not want the
3-tier model. They want the application to be just a client-server model. I
am in the process of advising the clients to get on board with our 3-tier
architecture.

My question is, if I have to make the app a client-server model for this
client, what is the best approach. I am trying to avoid having two different
solutions - one based on n-tier and another on client-server model.

All suggestions will be highly appreciated.

Thanks

Raju...

答

Raju，

我建议您考虑一个逻辑/物理N层设计，它可以在三台机器上运行，或者只需在一台机器上运行。我假设你的

客户不想拥有两*立的机器而且他们不会因为有两个dll在运行同一台机器。这种类型的
灵活性是N层设计的目标之一。如果稍后，单个应用程序服务器过载，那么将后端

dll移动到另一个盒子应该是无痛的。

- Sancerre

Raju,

I suggest that you consider a logical/physical N-tier design that can
be run on three machines, or simply on one machine. I assume that your
client doesn''t want to have two separate machines and that they don''t
care that there are two dll''s running on the same machine. This type of
flexibility is one of the goals of N-tier design. If, at a later time,
the single app server is getting overloaded, then moving the back end
dll to another box should be painless.

-- Sancerre

" Sancerre" &LT; SA ****** @ gmail.com&GT;在新闻中写道：1121176132.918157.85210

@ g47g2000cwa.googlegroups.com：

"Sancerre" <sa******@gmail.com> wrote in news:1121176132.918157.85210
@g47g2000cwa.googlegroups.com:

我建议你考虑一个逻辑/物理N层设计，它可以成为在三台机器上运行，或者只在一台机器上运行。我假设你的客户不想拥有两*立的机器，并且他们并不关心在同一台机器上运行两个dll。这种灵活性是N层设计的目标之一。如果稍后，单个应用程序服务器过载，那么将后端
dll移动到另一个框应该是无痛的。

I suggest that you consider a logical/physical N-tier design that can
be run on three machines, or simply on one machine. I assume that your
client doesn''t want to have two separate machines and that they don''t
care that there are two dll''s running on the same machine. This type of
flexibility is one of the goals of N-tier design. If, at a later time,
the single app server is getting overloaded, then moving the back end
dll to another box should be painless.

我同意Sancerre。我刚刚将这些发布在另一个帖子中，但它们也适用于此处，实际上可能是

帮助您的客户理解：

http://www.codeproject.com/gen/desig...inessLogic.asp

和

http：/ /www.codeproject.com/useritems/TierPressure.asp

-

Chad Z. Hower（又名Kudzu） - http://www.hower.org/Kudzu/

编程是反击的艺术形式

让你的ASP.NET应用程序运行得更快
http://www.atozed.com/IntraWeb/

I agree with Sancerre. I just posted these in another thread but they apply here too and may in fact
help your customer understand:

http://www.codeproject.com/gen/desig...inessLogic.asp

and

http://www.codeproject.com/useritems/TierPressure.asp
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Make your ASP.NET applications run faster
http://www.atozed.com/IntraWeb/

I同意Sancerre。实际上，客户端 - 服务器实际上是一层的b $
架构。您应该使您的应用程序足够灵活，以便能够以N层分发。

祝您好运！

-

Juan Romero

--------------------------- --------------

成功的人有做坏事的习惯，不喜欢

。

EM Gray

" Sancerre"写道：

I also agree with Sancerre. In fact, client-server is really a 1 Tier
architecture. You should make your application flexible enough to be able to
be distributed in N-tiers.

Good luck!

--
Juan Romero
-----------------------------------------
The successful person has the habit of doing the things failures don''t like
to do.
E.M. Gray
"Sancerre" wrote:

Raju，

我建议你考虑一个可以在三台机器上运行的逻辑/物理N层设计，或者只需一台机器。我假设你的客户不想拥有两*立的机器，并且他们并不关心在同一台机器上运行两个dll。这种灵活性是N层设计的目标之一。如果稍后，单个应用服务器过载，那么将后端移动到另一个盒子应该是无痛的。

- Sancerre >

相关推荐