Communication between tiers

[Markus R.]

Hi,

we are about to design an 3-tier web application. The web server
(presentation layer), the application server and the database systems will
be on separate physical machines. My question is about the communication
between the web server and the application server. I know two .NET builtin
ways to manage this communication. We could implement web services, we could
use remoting. Are there any additional opportunities to do this (besides
inventing an own communication protocol :-).
Further I want to ask you: How did you implement this interface in your
recent projects? What where the facts that lead to your decision? Are you
still happy with this decision? Where are its advantages and disatvantages?
Although I can imagine some of the answers I am very interested what others
have experienced in their real life.

Regards,

Markus

[Li-fan Chen]

Hi Markus,

The whole n-tier exercise is to achieve higher scalability. MSMQ is an oft
used method to dispatch jobs from the web tier to the application tier. It
provides job throttling as well as job distribution over N-number of
application servers.

Best personal regards,
-- Li-fan

--
Li-fan Chen
Software analyst/developer, Entrepreneur
Markham, Ontario, Canada
"Markus R." <ma*****@newsgroups.nospam> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

Hi,

we are about to design an 3-tier web application. The web server
(presentation layer), the application server and the database systems will
be on separate physical machines. My question is about the communication
between the web server and the application server. I know two .NET builtin
ways to manage this communication. We could implement web services, we
could use remoting. Are there any additional opportunities to do this
(besides inventing an own communication protocol :-).
Further I want to ask you: How did you implement this interface in your
recent projects? What where the facts that lead to your decision? Are you
still happy with this decision? Where are its advantages and
disatvantages?
Although I can imagine some of the answers I am very interested what
others have experienced in their real life.

Regards,

Markus

[Li-fan Chen]

Hi Markus,

In addition to looking at MSMQ. Also try Service Broker in SQL Server 2005.

Best personal regards,
-- Li-fan

--
Li-fan Chen
Software analyst/developer, Entrepreneur
Markham, Ontario, Canada
"Markus R." <ma*****@newsgroups.nospam> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

Hi,

we are about to design an 3-tier web application. The web server
(presentation layer), the application server and the database systems will
be on separate physical machines. My question is about the communication
between the web server and the application server. I know two .NET builtin
ways to manage this communication. We could implement web services, we
could use remoting. Are there any additional opportunities to do this
(besides inventing an own communication protocol :-).
Further I want to ask you: How did you implement this interface in your
recent projects? What where the facts that lead to your decision? Are you
still happy with this decision? Where are its advantages and
disatvantages?
Although I can imagine some of the answers I am very interested what
others have experienced in their real life.

Regards,

Markus

[Yuan Ren[MSFT]]

Hi Markus,

Thanks for posting!

For the current issue, there are many ways to achieve the distribution
system in .NET application. As Li-Fan mentioned, the MSMQ is a one choice.
However, I usually use the .NET Remoting or Web Service in my project
because of usability and scalability. The article below explains how to
make a choice between .NET Remoting and Web Service:
http://msdn.microsoft.com/library/de...us/dnbda/html/
bdadotnetarch001.asp

I hope this will be helpful. Thanks for your understanding!

Regards,

Yuan Ren [MSFT]
Microsoft Online Support