.NET Remoting vs Web Services

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

What are the factors that I should consider in choosing .NET Remoting vs Web
Services when an application will be deveoped using .net 2.0 and above? I
think I need to consider at least the following factors:

Performance
Security
Cost of Implementation
Cost of Maintenance
Technical Skills (what are the skills needed in .net remoting and Web
Services?)
 
Hello Peter,

see my answers below.

P> What are the factors that I should consider in choosing .NET Remoting
P> vs Web Services when an application will be deveoped using .net 2.0
P> and above? I think I need to consider at least the following
P> factors:
P>
P> Performance

good in both cases. read there http://msdn2.microsoft.com/en-us/library/ms996381.aspx
if your consider to use the remoting in cases except the intranet/binary
then the web services performance is equal to remoting

P> Security

WS is more usable (declarative) and has standard (WS-*) specifications

P> Cost of Implementation

WS is fastier (declarativeness)

P> Cost of Maintenance

WS. Migrating to the WCF is more changeless


---
WBR, Michael Nemtsev [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
 
Hi,

I think that Remoting is used with clients using .net framework (all of
them) while web services are more general but less efficient than remoting.

So if your application will communicate with other clients developed with
..NET I recommend using remoting for efficience and faster development. If it
has to 'talk' with unknown apps in the future you may consider doing it with
web services.

I'm very far to have a deep knowledge about this stuff but I think this is
the basic idea. I hope it helps,
 
Hi Michael,

It seems WS is better. What are some main reasons for people to use .net
remoting? Based on .net 3.0, does it seem that MS is promoting/enhancing WS
but .net remoting?

Peter
 
Hello Peter,

..net was used instead of DCOM, generally.

---
WBR, Michael Nemtsev [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

P> Hi Michael,
P>
P> It seems WS is better. What are some main reasons for people to use
P> .net remoting? Based on .net 3.0, does it seem that MS is
P> promoting/enhancing WS but .net remoting?
P>
P> Peter
P>
P> "Michael Nemtsev" wrote:
P>
Hello Peter,

see my answers below.

P> What are the factors that I should consider in choosing .NET
Remoting
P> vs Web Services when an application will be deveoped using .net
2.0
P> and above? I think I need to consider at least the following
P> factors:
P>
P> Performance
good in both cases. read there
http://msdn2.microsoft.com/en-us/library/ms996381.aspx
if your consider to use the remoting in cases except the
intranet/binary
then the web services performance is equal to remoting
P> Security

WS is more usable (declarative) and has standard (WS-*)
specifications

P> Cost of Implementation

WS is fastier (declarativeness)

P> Cost of Maintenance

WS. Migrating to the WCF is more changeless

---
WBR, Michael Nemtsev [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
Click to expand...
Click to expand...
 
Back
Top