Re: .Net remoting or COM+ ?
From: Paul Glavich [MVP - ASP.NET] (glav_at_aspalliance.com-NOSPAM)
Date: 10/17/04
- Next message: Paul Glavich [MVP - ASP.NET]: "Re: Com+ remote calls"
- Previous message: Paul Glavich [MVP - ASP.NET]: "Re: Reporting tools"
- In reply to: Daniel Carbajal [MVP]: "Re: .Net remoting or COM+ ?"
- Next in thread: richlm: "Re: .Net remoting or COM+ ?"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 17 Oct 2004 21:28:11 +1000
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.
-- - Paul Glavich Microsoft MVP - ASP.NET "Daniel Carbajal [MVP]" <DanielCarbajal@msn.com> wrote in message news:u4Yh3lprEHA.2596@TK2MSFTNGP12.phx.gbl... > 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 > > > "Azerty123" <ikke@hier.com> wrote in message > news:HHO9d.273224$1g2.14049377@phobos.telenet-ops.be... > > 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! > > > >
- Next message: Paul Glavich [MVP - ASP.NET]: "Re: Com+ remote calls"
- Previous message: Paul Glavich [MVP - ASP.NET]: "Re: Reporting tools"
- In reply to: Daniel Carbajal [MVP]: "Re: .Net remoting or COM+ ?"
- Next in thread: richlm: "Re: .Net remoting or COM+ ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
