February 10, 2010

Difference between .NET Remoting and ASP.NET web services

Difference between .NET Remoting and ASP.NET web services


ASP.NET Web Services.NET Remoting
Protocol Can be accessed only over HTTPCan be accessed over any protocol (including TCP, HTTP, SMTP and so on)
State ManagementWeb services work in a stateless environmentProvide support for both stateful and stateless environments through Singleton and SingleCall objects
Type SystemWeb services support only the datatypes defined in the XSD type system, limiting the number of objects that can be serializedUsing binary communication, .NET Remoting can provide support for rich type system
Interoperability Web services support interoperability across platforms, and are ideal for heterogeneous environments.NET remoting requires the client be built using .NET, enforcing homogenous environment.
Reliability Highly reliable due to the fact that Web services are always hosted in IISCan also take advantage of IIS for fault isolation. If IIS is not used, application needs to provide plumbing for ensuring the reliability of the application.
Extensibility Provides extensibility by allowing us to intercept the SOAP messages during the serialization and deserialization stages.Very extensible by allowing us to customize the different components of the .NET remoting framework.
Ease-of-Programming Easy-to-create and deployComplex to program.