none
wcf rest vs soap RRS feed

Answers

  • you can find your answer in the following article.

    http://msdn.microsoft.com/en-us/library/vstudio/hh273094(v=vs.100).aspx

    • Proposed as answer by Mernández Friday, July 26, 2013 6:37 AM
    • Marked as answer by Professo Thursday, August 1, 2013 1:50 AM
    Friday, July 26, 2013 6:37 AM
  • Hi,

    SOAP stands for "Simple Object Access Protocol", is a standard protocol specification for exchanging structured information in the implementation of WebService. This protocol is mainly rely on XML for it message format and message exchange. So other system interact with WebService in  a prescribed manner defined by SOAP. 

    Rest stands for Representational State Transfer. REST attempts to describe architectures that use HTTP or similar protocols by constraining the interface to a set of standard operation like GET, POST, PUT, DELETE for HTTP). Here, the focus is on interacting with stateful resources, rather than messages or operations.

    Areas where SOAP based WebServices is a great solution:

    Asynchronous processing and invocation: If application needs a guaranteed level of reliability and security then SOAP 1.2 offers additional standards to ensure this type of operation. Things like WSRM – WS-Reliable Messaging etc.
    Formal contracts: If both sides (provider and consumer) have to agree on the exchange format then SOAP 1.2 gives the rigid specifications for this type of interaction.
    Stateful operations: If the application needs contextual information and conversational state management then SOAP 1.2 has the additional specification in the WS* structure to support those things (Security, Transactions, Coordination, etc). Comparatively, the REST approach would make the developers build this custom plumbing.          

    Areas where RESTful WebServices are a great choice:


    Limited bandwidth and resources: Remember the return structure is really in any format (developer defined). Plus, any browser can be used because the REST approach uses the standard GET, PUT, POST, and DELETE verbs. Again, remember that REST can also use the XMLHttpRequest object that most modern browsers support today, which adds an extra bonus of AJAX.
    Totally stateless operations: If an operation needs to be continued, then REST is not the best approach and SOAP may fit it better. However, if you need stateless CRUD (Create, Read, Update, and Delete) operations, then REST is suitable.
    Caching situations: If the information can be cached because of the totally stateless operation of the REST approach, this is perfect.

    For more information, please try to refer to:
    http://onlydifferencefaqs.blogspot.in/20...stful.html .

    Best Regards.


    Amy Peng
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, July 26, 2013 8:28 AM
    Moderator

All replies

  • you can find your answer in the following article.

    http://msdn.microsoft.com/en-us/library/vstudio/hh273094(v=vs.100).aspx

    • Proposed as answer by Mernández Friday, July 26, 2013 6:37 AM
    • Marked as answer by Professo Thursday, August 1, 2013 1:50 AM
    Friday, July 26, 2013 6:37 AM
  • Hi,

    SOAP stands for "Simple Object Access Protocol", is a standard protocol specification for exchanging structured information in the implementation of WebService. This protocol is mainly rely on XML for it message format and message exchange. So other system interact with WebService in  a prescribed manner defined by SOAP. 

    Rest stands for Representational State Transfer. REST attempts to describe architectures that use HTTP or similar protocols by constraining the interface to a set of standard operation like GET, POST, PUT, DELETE for HTTP). Here, the focus is on interacting with stateful resources, rather than messages or operations.

    Areas where SOAP based WebServices is a great solution:

    Asynchronous processing and invocation: If application needs a guaranteed level of reliability and security then SOAP 1.2 offers additional standards to ensure this type of operation. Things like WSRM – WS-Reliable Messaging etc.
    Formal contracts: If both sides (provider and consumer) have to agree on the exchange format then SOAP 1.2 gives the rigid specifications for this type of interaction.
    Stateful operations: If the application needs contextual information and conversational state management then SOAP 1.2 has the additional specification in the WS* structure to support those things (Security, Transactions, Coordination, etc). Comparatively, the REST approach would make the developers build this custom plumbing.          

    Areas where RESTful WebServices are a great choice:


    Limited bandwidth and resources: Remember the return structure is really in any format (developer defined). Plus, any browser can be used because the REST approach uses the standard GET, PUT, POST, and DELETE verbs. Again, remember that REST can also use the XMLHttpRequest object that most modern browsers support today, which adds an extra bonus of AJAX.
    Totally stateless operations: If an operation needs to be continued, then REST is not the best approach and SOAP may fit it better. However, if you need stateless CRUD (Create, Read, Update, and Delete) operations, then REST is suitable.
    Caching situations: If the information can be cached because of the totally stateless operation of the REST approach, this is perfect.

    For more information, please try to refer to:
    http://onlydifferencefaqs.blogspot.in/20...stful.html .

    Best Regards.


    Amy Peng
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, July 26, 2013 8:28 AM
    Moderator