none
Advantages of WCF Service Over distributed technologies like .NET Remoting/MSMQ/Web Service/Com+

    Question

  • Hi All,

     

    I have gone through lots of site on WCF and found that every one is talking about

    1.Integration of the WCF Service with existing technologies as the advantage.... Smile

     

    I would like to know what are the other advantages of the WCF Service over each distributed communication technologies like - .NET Remoting /MSMQ/COM+/Web Service.

     

    any kind of help will be appreciated.

     

    Thanks,

    Vinod Sa.

    *Happy Holy days ****

     

     

     

     

    Tuesday, December 25, 2007 11:44 AM

Answers

  • Although I understand the nature of your question, please allow me to reframe it. WCF does not replace MSMQ, COM+ or Web Services. so it doesn't make sense to compare them in the manner you've laid out. WCF provides a declarative infrastructure for all forms of communication to and from the Windows platform. It is inclusive of nearly all of the technologies that you asked about rather than being in competition with them (remoting being a noted exception). Using WCF, communications happen at designated service endpoints, and an endpoint can implement different protocols (such as Web Service (presumably you meant asmx style here), WS-* SOAP style services), encodings (such as Text, Binary & MTOM), and transports (such as MSMQ, Http, etc.). Services can be accessible through multiple endpoints, thus providing the capability for a single service to be simultaneously accessed via multiple protocols and transports. With .net 3.5, it becomes even easier to provide RESTful endpoints (JSON, POX, RSS, ATOM). Building services that can be consumed by a web client as JSON while simultanously being accessed by a business partner through the internet using the SOAP protocol (with its full compliment of WS-* implementations such as WS-Security, WS-ReliableMessaging, etc.) is very powerful leverage.

     

    .NET Remoting is an obsolete technology (no improvements since .net 1.1, and none are planned).

     

    --Paul Mehner

     

     

     

     

     

     

    Thursday, December 27, 2007 2:12 AM

All replies

  • WCF is interoperable with other services in compared to .Net Remoting where the client and service have to be .Net. WCF services provide better reliability and security in compared to ASMX web services.

     

     

    Wednesday, December 26, 2007 8:23 PM
    Moderator
  • Although I understand the nature of your question, please allow me to reframe it. WCF does not replace MSMQ, COM+ or Web Services. so it doesn't make sense to compare them in the manner you've laid out. WCF provides a declarative infrastructure for all forms of communication to and from the Windows platform. It is inclusive of nearly all of the technologies that you asked about rather than being in competition with them (remoting being a noted exception). Using WCF, communications happen at designated service endpoints, and an endpoint can implement different protocols (such as Web Service (presumably you meant asmx style here), WS-* SOAP style services), encodings (such as Text, Binary & MTOM), and transports (such as MSMQ, Http, etc.). Services can be accessible through multiple endpoints, thus providing the capability for a single service to be simultaneously accessed via multiple protocols and transports. With .net 3.5, it becomes even easier to provide RESTful endpoints (JSON, POX, RSS, ATOM). Building services that can be consumed by a web client as JSON while simultanously being accessed by a business partner through the internet using the SOAP protocol (with its full compliment of WS-* implementations such as WS-Security, WS-ReliableMessaging, etc.) is very powerful leverage.

     

    .NET Remoting is an obsolete technology (no improvements since .net 1.1, and none are planned).

     

    --Paul Mehner

     

     

     

     

     

     

    Thursday, December 27, 2007 2:12 AM
  • The advantages of WCF is clearly evident once we see the power it delivers to products not only during development, but also in implementation and maintanence.

    Let me explain as to what I am trying to convey:
    1. WCF clearly demarcates development and implementation. All the development part lies in the code while the implementation like the binding you choose or the security model you embrace can be handled in the config file. COM+ or realted technologies will not give you this advantage. This is what WCF means when it says they reduce plumbing time. Developer concentrates on what he wants to achieve and WCF takes care of delivering it to the outer world in the most reliable, secure and high performance fashion. WCF also scores over remoting by giving out of box solutions to publish code as Web services. The out of box solutions are more simple to implement and have less overheads.
    2. WCF opens up communication with other applications communicating from various platforms. The fast development power of .net combined with the fast delivery power of WCF makes the market reach time very minimal. Along with this when we add inter operatability, WCF simply reaches out further. This statement doesn't mean that a WCF service runs on Linux but can talk to any app written based on certain set of protocols specified by WCF. In the Web world this means it is available on every major browser. With other technologies, achieving the same requires lots of tweaking but it is available out of box when you embrace WCF.
    3. Hosting a WCF service is very simple on IIS 7 or WAS in Vista or WIN 2K8. In WIN 2K3 and WIN XP SP2 it can be hosted on IIS 6 for the HTTP mode and as a  WIndows service or even self hosting will do.  To achieve the same too it takes minimal efforts.
    4. WCF has an integrated Logging mechanism that helps you log traces that become a boon during maintanence. In other technologies, developer has to do some work to achieve this but in WCF, all that we have to do is to enable trace by changing the config file and WCF starts providing traces for you.
    5. Security mechanism in WCF is fairly simple and out of box when you look from the implementors perspective but is very robust and highly secure. The best part is that for the highy used and recommended bindings, WCF provides default security which can be trusted to the core. The message security on WSHTTPbinding is an example on these lines.

    Over all to conclude I would say if you are with MS technologies and plan to stick to same in the long run, then WCF is something you should not miss to embrace. The performance and other data points that I convey here are my personal experience during integration of our product (which is 11 years old and has almost all flavours of MS technologies) with WCF.
    Thursday, January 17, 2008 6:14 AM
  • Moreover it is an framework to develop Service Oriented applications under microsoft platform mixing both message and rpc style of programming.Through this we can achieve platform optimization through binary as well as open standards-based communications.
    • Proposed as answer by fercho0011 Thursday, March 19, 2009 12:31 PM
    Thursday, January 17, 2008 7:06 AM
  • Hi, just in this moment i will search in everywhere about WCF capabilities and Nobody can tell how to do this:

    if i have many bussiness classes and i usethem in my client side.. in remoting i can use marshall by ref and easy way can make everithing invocation.. BUT in WCF you can't do that WCF is unable to do that you have to change all your architecture to use it and make some many class as services... imagine a application that has over 70 bussiines classes i'will be converted in 70 wcf services? or change so many code? WCF can't support all the .net Remoting capabilities.... so Remoting isn't so Obsolete ..... 
    • Proposed as answer by Zig0830 Friday, April 10, 2009 5:41 PM
    Thursday, March 19, 2009 12:38 PM
  • Sunday, September 27, 2009 10:26 PM
  • @Vinod sa
    I think paul states exactly what Microsoft says that why it comes up with WCF despite already having other distributed application technologies. WCF doesn't actually replaces them but comes up with something that integrates all of them. Well the point is that for every scenario you had something or other like remoting or web services but then Microsoft comes up with WCF as a technology to fit all the cases. Basically it supports all the protocols which was not the case to be before. Moreover you might had to integrate one or more technologies into a project like once we were using remoting in a project but suddenly we had to transfer a hashtable and remoting goes kaboom. It doesn't support non serializeable objects so we had to create a web service for it. WCF comes to rescue for such situations as it tends to be a technology fitting everywhere and useable with any language over any protocol. Ya but still there are some performance issues under certain scenarios for which you better have a look at the link below
    http://msdn.microsoft.com/en-us/library/bb310550%28lightweight%29.aspx

    Dipin Behl MCTS
    • Proposed as answer by Dipin Behl Tuesday, December 22, 2009 6:26 AM
    Friday, December 04, 2009 10:21 AM
  • What is the relation are Remoting and WCF
    Saturday, March 24, 2012 5:32 AM
  • A major advantage  is that WCF allows a single consistent access to windows communication technologies for developers thereby enabling easier development of SOA applications. Microsoft has abstracted a lot of the plumbing work so as to enable this.
    Saturday, March 24, 2012 5:38 AM
  • What is the relation are Remoting and WCF

         I would like to know that what is the use of SOA.Please who can clarify my question.Please post one perfect answer as a devloper understanding

    Saturday, March 24, 2012 5:41 AM
  • What is the relation are Remoting and WCF

         I would like to know  what is the use of SOA.Please who can clarify my question.Please post one perfect answer as a devloper understanding


    Saturday, March 24, 2012 5:41 AM
  • What is the relation are Remoting and WCF

         I would like to know  what is the use of SOA. who can clarify my question.Please post one perfect answer as a devloper understanding



    Saturday, March 24, 2012 5:42 AM
  • Although I understand the nature of your question, please allow me to reframe it. WCF does not replace MSMQ, COM+ or Web Services. so it doesn't make sense to compare them in the manner you've laid out. WCF provides a declarative infrastructure for all forms of communication to and from the Windows platform. It is inclusive of nearly all of the technologies that you asked about rather than being in competition with them (remoting being a noted exception). Using WCF, communications happen at designated service endpoints, and an endpoint can implement different protocols (such as Web Service (presumably you meant asmx style here), WS-* SOAP style services), encodings (such as Text, Binary & MTOM), and transports (such as MSMQ, Http, etc.). Services can be accessible through multiple endpoints, thus providing the capability for a single service to be simultaneously accessed via multiple protocols and transports. With .net 3.5, it becomes even easier to provide RESTful endpoints (JSON, POX, RSS, ATOM). Building services that can be consumed by a web client as JSON while simultanously being accessed by a business partner through the internet using the SOAP protocol (with its full compliment of WS-* implementations such as WS-Security, WS-ReliableMessaging, etc.) is very powerful leverage.

    .NET Remoting is an obsolete technology (no improvements since .net 1.1, and none are planned).

    --Paul Mehner


         I didn't understand ,what is JSON
    Saturday, March 24, 2012 5:44 AM