architecture question

  • Thread starter Thread starter Ambarish Ganguly
  • Start date Start date
A

Ambarish Ganguly

Hi,

We are planning for a 3 tier architecture with
Web server
App server containing all business dlls
Database server.

The web server will communicate using COM interop ( CreateObject sort of things) with app server where the .NET components will be in COM+.

Have any of you tried this sort of architecture? Any tips, tricks, suggesstions, advantages, disadvantages, loop holes anything which provides insight would be highly helpful.

Thanks a ton!

-Ambarish
 
You don't need to use the "CreateObject" type of setup
with .NET anymore. There are a couple ways to handle this:
1. Host the components in COM+ and use remoting to access
them (I realize that the documentation is pretty sparse
considering this is just about as complicated an
architecture as you can get) (and you can even use IIS to
host the remoting part).
2. Create Web Services and use the transaction
capabilities of WS-I (however, the transaction
specification is new and may not be complete, I haven't
checked lately).

Hope this helps a little.

Jeff Levinson

Author of "Building Client/Server Applications with
VB.NET: An Example Driven Approach"
-----Original Message-----
Hi,

We are planning for a 3 tier architecture with
Web server
App server containing all business dlls
Database server.

The web server will communicate using COM interop (
Click to expand...
CreateObject sort of things) with app server where
the .NET components will be in COM+.
Have any of you tried this sort of architecture? Any
Click to expand...
tips, tricks, suggesstions, advantages, disadvantages,
loop holes anything which provides insight would be
highly helpful.
 
Back
Top