COM+ vs. .Net Remoting -- dotnet remoting

anonymous NO[at]SPAM discussions.microsoft.com
11/24/2003 5:05:23 PM

COM+ provides many services such as transactions, object
pooling, role based security that require setting up of
contexts and such which affect performance. I assume you
are using DCOM to talk to the COM+ components and DCOM is
pretty much on par with remoting in terms of speed (yes I
know there are differences but relative to this
discussion, they are only minor) so COM+ is slower
because of the extra services it offers and its initial
contruction of these contexts to support these services.
If you host outside of COM+, then it will be faster,
whether by DCOM or remoting. If using remoting, but still
want COM+ services, you wont see much performance
difference. Depending on the remoting config and the
nature of the remote conversation, is where you'll see
differences in prformance for DCOM and remoting.

- Paul Glavich

[quoted text, click to view]

mjamil314 NO[at]SPAM hotmail.com
11/27/2003 1:21:20 PM

Well, my component cannot be stateless. Actually, it should be
singleton, i.e., all clients should refer to the same component since
the component holds and controls the status of a real-time data
acquisition system. It seems from the posts that .Net would not add
much to the performance of my application.

What about deployment and support? deployment COM+ seems to be more
technically involved, especially, if COM+ events have to propagated
though the network as in my case. Furthermore, there seems to be some
compatibiliy issues between COM+ 1.0 (Win2K) and COM+ 1.5 (WinXP).
This is important because my application would be deployed overseas by
people whose technical skills I'm not familiar with. It seems .Net
remoting would be easy to deploy and support.

I would appreciate any further thoughts and comments...

[quoted text, click to view]

Pete Davis
11/27/2003 2:58:03 PM

As the other person responded, the speed is fairly similar for
communications.

It really depends on how you implemented in COM+ vs. how you implement the
remoting. Are you using object pooling? Are your components stateless? In
our own COM+ application, by using a combination of pooling and stateless
components, we were able to acheive very acceptable performance levels. We
also separated transactional code from non-transactional code. So, for
example, a component which read data from the database would be completely
separate from a component that wrote that same data back to the database,
the reader being non-transactional and the writer being transactional.

Under .NET Remoting, you don't have that kind of infrastructure, or at least
not as integrated for that kind of work. The disadvantage is that any sort
of pooling you do is going to have to be home-brewed, and transactional work
will require a bit more effort. On the other hand, you can fine-tune
everything for your particular app.

Pete

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet remoting

dotnet remoting : COM+ vs. .Net Remoting