What do you use for Application Server?

[Guest]

In Microsoft architecture diagrams, I always see 3 layers of application
structure: web server, application server and database server.

Web server is IIS. Database server is SQL server.

What do you use for application server? COM+ server is for COM interface
which is not ideal for .NET applications. Web service and .NET Remoting is
for communicating with other applications which is not ideal for a layer of
application structure.
Can anybody give some comments or suggestions?

Thanks a lot.

 

[Radek Cerny]

I wrote my own.
See http://www.c1s.com.au/C1prod/files/Whitepaper.pdf (topology with
AppServers on page 2).

 

[Michael Nemtsev]

Hello BF,

..NET has the EnterpriseServices, the new namespace with use the COM+ features.
It's the standard set of services to build application server.

If the EnterpriseServices features are not enough for your task look at BizTalk
Server.

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

B> What do you use for application server? COM+ server is for COM
B> interface which is not ideal for .NET applications.
B>

 

[Guest]

Thanks for the reply.

But EnterpriseServices uses COM+ server which is not ideal to use as .NET
application server because it uses COM interface and it does not support
parameterized constructors.

I checked many articles on the internet. They all say COM+ server should be
used within your service if you need object pooling ... To get good
performance, we have to use COM+ server on the same server as the web server,
which is not doable if I use web farm for my web application.

So it looks like Microsoft actually does not have application server which
is good to use for .NET applications! Those application servers on
architecture diagrams are actually just to make them look good.