Dennis Bottjer | ASP.NET + SharePoint Architect, Trainer & Speaker

"An Ounce of Prevention is Worth a Pound of Cure" - Ben Franklin
posts - 168, comments - 59, trackbacks - 41

My Links

News

Add to Technorati Favorites The views expressed in this blog are mine and mine alone, not that of my employer, Microsoft, or anyone else’s. No warrantee is given for the quality of any material on this site.

Tag Cloud

Archives

Post Categories

SOA: Deciding Between Web Services and Remoting

On a recent project I had a choice between using Web Services and Remoting.  http://www.thinktecture.com/Resources/RemotingFAQ/default.html is an excellent resource about remoting.  In the end I chose Web Services but I think it is interesting to understand why.  First .NET Remoting is a good technology for interprocess communication when developing purely in the .NET environment.  Next, .NET Remoting is very fast when serializing binary data over TCP.  Remoting is also a good choice when you are operating on an internal LAN. 

I was work in a pure .NET Environment and I needed for my web application to validate Routing Numbers.  I choose to build a Web Service for several reasons.

  • Web Services is standards based (XML, WS-I, DISCO, WSDL, etc.)
  • Web Services are easy to consume.  Just add a web reference.  This reference can be dynamic. (Set in web config.)
  • Have strong industry support
  • Still Fast
  • Easier to understand for a less skilled deverloper than Remoting.
  • Web Services Scale Better.  Use of the web service could easily be given to customers at a later date.

Print | posted on Wednesday, August 03, 2005 1:20 AM |

Comments have been closed on this topic.

Powered by: