Architecture Question

[Tom]

Hello,

I have a Windows form application that currently uses a database local to
the machine it is running on. We are planning on setting this application
up for a multi-user environment, so I would like to change to a 3-tier
architecture application for scalability:

1. My Client
|
2. My Business Logic Server (The client connects here)
|
3. My database server

We may also create another web form client in the future, and I would also
like that to connect to the business logic server as well.

My question is, what type of communication do you guys recommend between the
exist client and the business logic server?

1. If I use .NET remoting, can an ASP .NET page easily utilize the .NET
remoting code if I create an additional web form in the future?

2. If I setup the logic server to provide web services to clients, I have
heard that web services don't support transactions across multiple database
servers, so if I can't use web services, what should I use?

Any help is greatly appreciated. Thanks.
-- Tom

 

[sloan]

This post is a DUPLICATE.

There is a 1:18 PM Post (a few hours after this one).

............

I've made a reply there

 

[Tom]

Thanks sloan. I'm newsgroup challenged. I'll reply to your other message.

 

[Cowboy \(Gregory A. Beamer\)]

Hello,

I have a Windows form application that currently uses a database local to
the machine it is running on. We are planning on setting this application
up for a multi-user environment, so I would like to change to a 3-tier
architecture application for scalability:

1. My Client
|
2. My Business Logic Server (The client connects here)
|
3. My database server

We may also create another web form client in the future, and I would also
like that to connect to the business logic server as well.

My question is, what type of communication do you guys recommend between
the exist client and the business logic server?

1. If I use .NET remoting, can an ASP .NET page easily utilize the .NET
remoting code if I create an additional web form in the future?

Yes, but I would not head this direction. Better to use WCF (.NET 3.x) and
set up a "web service". You can more easily change the transport this way.
This gives you the best of both worlds: speed and simplicity.

2. If I setup the logic server to provide web services to clients, I have
heard that web services don't support transactions across multiple
database servers, so if I can't use web services, what should I use?

Hold on a second here.

If you send a complete message, you can span multiple databases. The web
service, in this instance, is just a messaging interface. Realize, of
course, that any transactions spanning databases are difficult, no matter
how you link them.

If you mean you cannot call multiple methods (on possibly multiple web
services) and have them linked in a single transaction, you are correct.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************