Web Services Technology Protocol: REST and soap

The Web Service technology has SOAP (Simple Object access Protocol, easy Objects accessing protocol) and rest (representational state Transfer, presentation status transfer)

REST: A scheme that is invoked with a standard URI. The client's application obtains a representation of the resource through a URI. Obtaining these representations causes these applications to transform their state. If you need a stateless crud (create/read/update/delete, create/read/update/delete) operation, then rest should be used.

Advantages:

1. Rest is easy to understand

2. Support the HTTP/HTTPS client/server as long as it is supported

3. The returned structure can be in any format (defined by the developer)

Disadvantages:

Lack of standards and are therefore considered only as an architectural approach.

SOAP1.2:

Soap is inseparable from XML (extensible Markup Language, Extensible Markup Language) in three ways: the SOAP envelope (envelope) is XML-based, it defines what is in the message and how to handle it; a set of encoding rules for data types ; Process invocation and response planning. The SOAP envelope is emitted by the transport Protocol (HTTP/HTTPS), the RPC (remote Procedure call, remoted procedure calls) are executed, and an XML document is returned with the SOAP envelope.

If the application requires contextual information and dialog state management, then soap should be used.

Advantages:

1. Based on the "generic" transport protocol. Rest is currently based on HTTP/HTTPS, while soap can support any transport protocol.

2. Well-defined agreements and a set of well-established rules

Disadvantages:

XML is also a disadvantage because XML is lengthy and time-consuming to parse.

Web Services Technology Protocol: REST and soap