.Net remoting or COM+ ?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Azerty123 - 09 Oct 2004 11:03 GMT

Hi all,
I know this question has been asked many times already, but I still have
some questions.

We would like to use .net remoting for a new distributed application. I
understand that a few options are available for the host part (IIS, seperate
NT service, console app...).
IIS uses http channel which is slower than the TCP channel of an NT service,
but IIS supports authentication while you have to program this part yourself
using the second option.

We want a fast solution here, with integrated authentication that we do not
have to program ourself. Do these 2 critera completly lock out .net
remoting?
Com+ seems to support authentication (correct me if i'm wrong), has some
overhead but is still faster than .net remoting using IIS?

My question is, should I choose com+ for security and speed? why(not)
If a better solution would be .net remoting, how do I overcome the IIS
"speed" problem and the NT service security problem?

I hope someone could clear up these things for me...

thanks in advance!

Reply to this Message

Sam Santiago - 09 Oct 2004 21:36 GMT

Where have you read about the IIS "speed" problem? I think .NET Remoting,
using HTTP, and the binary formatter can perform as good or better than
COM+. All COM+ calls require a COM Interop call, so there's a performance
hit there.

Check out these articles:

This article has performance numbers for the various options of remoting -
IIS vs Windows Service (WS) and binary vs. SOAP:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/bdad
otnetarch14.asp

.NET Remoting Security
http://msdn.microsoft.com/library/en-us/secmod/html/secmod11.asp?frame=true#secm
od11_authentication

Improve Remoting Performance
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scal
enetchapt11.asp

Thanks,

Sam

Signature

_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com
http://www.SoftiTechture.com
_______________________________

> Hi all,
> I know this question has been asked many times already, but I still have
[quoted text clipped - 20 lines]
>
> thanks in advance!

Reply to this Message

Daniel Carbajal [MVP] - 10 Oct 2004 08:19 GMT

Well, Microsoft recommend using Web Services, but they are really very slow,
we have done benchmark tests and Enterprise Services (COM+) are as faster as
.NET Remoting Binary TCP Channels and also ES have many good features such
as object pooling, declarative and distributed transactions, role-based
security and queued components.
Regards,
Daniel Carbajal
Microsoft MVP

> Hi all,
> I know this question has been asked many times already, but I still have
[quoted text clipped - 20 lines]
>
> thanks in advance!

Reply to this Message

TinaE - 11 Oct 2004 10:59 GMT

Microsoft recommends Web Services, because Web Services have been earmarked
as the future technology for interop and remoting. At the moment the
performance is still poorer than .Net Remoting and COM+, but all indications
are that WS will become much better performers with the release of Longhorn,
as WS will be natively supported (I hope I understood correctly, otherwise I
am in deep trouble).

> Well, Microsoft recommend using Web Services, but they are really very slow,
> we have done benchmark tests and Enterprise Services (COM+) are as faster as
[quoted text clipped - 29 lines]
> >
> > thanks in advance!

Reply to this Message

Paul Glavich [MVP - ASP.NET] - 17 Oct 2004 12:28 GMT

A couple of things here.

1. Web services and .Net remoting (when used over the Http channel ie. via
IIS) are pretty much the same speed. Web services can even exceed .Net
remoting in this scenario (does't matter what formatter, but SOAP formatter
is slowest of all in .Net remoting).
2. .Net remoting using the TCP channel; is faster than Web services.
3. COM+ components by default, will use DCOM. DCOM is the fastest of all
these protocols. Currently, neither remoting (over any channel) or Web
services can match it for speed. It is only really used in Intranet
scenarios though as configuring a firewall to allow the right ports through
for DCOM to work can be tricky.
4 COM+ components/Enterprise Services/DCOM do have much better security
support. .Net remoting really has nothing at all. If you use .Net remoting
via IIS, you can take advantage of windows integrated authentication (which
itself slows things down a little due to the 5 way conversation that takes
place for a successfull authentication. Note: This is assuming NTLM,
Kerberos can be better but it depends). When using IIS, you also have the
option to use SSL for encrypting your traffic.
5. COM+ gives you some nice features that Daniel mentions below, but unless
you really want them, using COM+ might be overkill. To invoke a COM+
component requires some performance overhead, so even though DCOM might be
faster, the total time it takes for a remote call to get from client to end
of processing, might be longer via COM+. This is really something that needs
to be tested though, and cannot be measured generally.
6. Another consideration is WSE (Web Service Enhancements 2). The security
setup is relatively easy, and the performance is good. Its inline with
future direction, and is well aligned to take advantage of Indigo
technology, when its made available which is "supposedly" going to match
across the wire performance, with that of DCOM, only its web services based.

Signature

- Paul Glavich
Microsoft MVP - ASP.NET

Reply to this Message

richlm - 13 Oct 2004 19:33 GMT

If you're fixed on going the remoting over TCP route, you will find the
following 2-part sample useful.

.NET Remoting Authentication and Authorization Sample - Part I
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/r
emsspi.asp

.NET Remoting Authentication and Authorization Sample - Part II
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/r
emsec.asp

If you do go this route, you will have more recoding work to do moving to
Longhorn/Indigo, than if you choose WS or ES (or even remoting over http).

Reply to this Message

.Net remoting or COM+ ?

Free Magazines