REST Vs SOAP

'Unless you have a definitive reason to use SOAP use REST'


REST :  REST is sweat spot when you are exposing the public API overt internet to handle the CRUD operation on the data.REST focuses on assessing the named resources through the  single consistent  Interface.


  SOAP:   SOAP brings it's own protocol and focuses on the exposing the pieces of application logic (not the data).SOAP focuses on accessing the named operation, which implements some business logic through different interfaces.
Though SOAP is commonly referred to as “web services” this is a misnomer. SOAP has very little if anything to do with the Web. REST provides true “Web services” based on URIs and HTTP.
 -Language, Platform ,protocol indepedent

Why REST ?
  1. REST  ( lightweight, ) has better performance and scalability .
  2.REST supports multiple data format XML,JSON etc.
  3.REST reads can be cached, while SOAP based read can not be cached.

Why SOAP ?

1. WS_SECURITY
  While SOAP supports SSL (just like REST) it also supports WS-Security which adds some enterprise security features. Supports identity through intermediaries, not just point to point (SSL). It also provides a standard implementation of data integrity and data privacy. Calling it “Enterprise” isn’t to say it’s more secure, it simply supports some security tools that typical internet services have no need for, in fact they are really only needed in a few “enterprise” scenarios.

2. WS_AUTOMIC_TRANSACTION

Rest doesn’t have a standard messaging system and expects clients to deal with communication failures by retrying. SOAP has successful/retry logic built in and provides end-to-end reliability even through SOAP intermediaries.
3. WS_MESSAGE_RELIBILITY 

4.WS_CO_ORDINATIOND


What is Integration ?

  Integration is process by which information is passed between tow or more distinct software entities.

THE CHOICE OF INTEGRATION MEDIA IS CATEGORICALLY IS DETERMINED WITH HELP OF FOLLOWING QUESTIONNAIRES.

1. Is transfer of information is synchronous or asynchronous ?
2. Is transfer of information acknowledged ?
3. Is transfer of information transactional ?
4. Does transfer of information requires message-level or transport-level  encryption ?
5.Does transfer of information occurs in batches composed of multiple message or one message at time ?
6. Does transfer of information occurs between system build using same technology or different technology ?
7. Does transfer of information use the technology-specific/transport protocol specific ?.


Java to Java  Integration
--------------------------
1. JMS  
1. JMS is interinsically designed for Asynchronous communication between between to java aplication.
   Features:
          1. publish subscribe and point to point messaging model.
          2. Message Delivery  Acknowledgement
          3.Message Level Encryption
          4.Distributed Transaction (JTA)

Java to Non-Java Integration :
------------------------------
  1.Web service are intrinsically designed to facilitate the integration of heterogeneous systems.
      1. Using web service is truly technology  independent .
     Which one embrace :
             1. SOAP
             2. Self Describing mesaage format Such as XML
         
    SOAP VS REST.   
 
https://dzone.com/articles/put-vs-post
https://knpuniversity.com/screencast/rest/put-versus-post

  Deciding between Put and POST

=======================

1. if the end point is idempotent .

2. URI must be addressed to resource being updated.

Patch :
  Update the resource without sending  all  the attributes in the request.