Before we start differentiate between SOAP vs ReST web services let’s understand what is web service?
According to web definition from WIKI –
“…A web service is a method of communication between two electronic devices over World Wide Web. It is a software function provided at a network address over the web with the service always on as in the concept of utility computing.”
In simple words – Web service is a mechanism that provides data as a service/response over the http protocol on request of some other programs.
What is the difference between web site and web service?
Most of the people don’t know the difference between web service and web site. The two looks similar but Web service is different than Web Site.
Web Site is something that presents data on a browser in human readable format. The web sites are meant for easy user navigation. These are basically HTML pages in human readable format when rendered on browser.
Web Service offers service to some other software applications. Upon receiving a request from these software applications it produces a response. This request can also contain some input data for the service to process and depending upon the input data it returns a result.
The result provided by web services are usually meant for software’s so that they can consume it, process it and optionally present well formatted data on the web site. The result produces by web services may or may not be easily readable by the humans. They are meant for software applications only. The popular result formats are XML and JASON. These popular formats are easy to parse and use.
A website may or may not use webservice.
Example of Website: You can go to website https://www.google.co.in/maps and use it to search a map for your address.
Example of Webservice: You have built your own website and on that website you want to show the address of your site visitor. In this case you can call a webservice provided by google maps, pass the desired address to this web service and it will return a map. And now you can show this map on your website.
I hope now you get the clear idea about what is web service and web site. Now let’s take a look at two different types of web services i.e. SOAP and ReST.
ReST and SOAP are the set of specification of information to be used in the implementation of web services. These are messaging protocols used to exchange the information between two programs. The exchange of information is one-way.
What are soap services? / What is soap service?
Simple Object Access Protocol (SOAP) is a XML based structured protocol specification to be used in the implementation of web service. In simple words SOAP web services uses XML as a mechanism for exchanging of information (one way) between the two programs (end points) over any transport layer protocol.
Though for message negotiation and transmission soap is not relies on any particular transport protocol but HTTP (Hyper Text Transfer Protocol) or SMTP (Simple Mail Transfer Protocol) are the two most popular transport protocols used with SOAP. Similarly SOAP is not relying on any particular programming language or operating system as far as they understand XML and SOAP message.
For example, one program running in Windows operating system such as Windows 7 can communicate to another program running in Linux operating system. For this soap will use XML and HTTP.
SOAP message is consist of three parts, i.e. envelope, header and body as shown in below image.
Simple SOAP Architecture
SOAP:envelope
The root element of SOAP message is a SOAP envelope which states what is in the soap message and how to process it. Application looks at the soap:envelope and easily determines what could be the SOAP message. It also helps application to identify the version of the SOAP being used.
SOAP:header
SOAP:Header is an optional element of the soap message. The element from this part contains application specific information. The information should be related to soap message and could be anything like authentication method or payment methods etc.
Though it is an optional element, but if present then it should be the first child element of the soap:envelope.
Though it is an optional element, but if present then it should be the first child element of the soap:envelope.
SOAP:body
SOAP:body is a mandatory element unlike soap header. This part contains all information related to call and response of the web service. Actual soap message goes here.
The format of soap message is as below –
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<!-- Header elements. -->
</soap:Header>
<soap:Body>
<!-- Body elements. -->
</soap:Body>
</soap:Envelope>
The most important aspect of the SOAP is that without making any changes to the original SOAP message it can tunnel through firewalls and proxies.
What are restful services? / What is restful service?
REST stands for REpresentational State Transfer is a newcomer in its type of family. REST provides very easy access and implementation to a web service that ultimately aims to work best on the web. Restful web services are an architecture style stateless web services mostly used for building client-server applications over HTTP.
In REST, every resource is addressed or accessed by Unique URI (Uniform Resource Identifier) and data and functionality forms a resource. Representation State Transfer defines some set of operations and resources acts according to these operations.
Instead of using XML for request/response, it relies on simple unique URI and that’s why it is also considered as lightweight alternative to SOAP. As it is rely on URI as a resource identifier, the standard CRUD operations of HTTP (GET, PUT, DELETE, POST, HEAD) can be performed on that URI/resource.
SOAP provides the response in XML format only while REST doesn’t have to use XML only. Though XML and HTML formats are often used for REST response, REST can also response in JASON, CSV and RSS formats. There are various options you can choose for the parsing of the REST response. Each of these responses has their own advantages and disadvantages.
“ReST” is lightweight service alternative to most of the mechanism including SAOP and RPC (Remote Procedure Call) but it has no “W3C” recommendations.
In short, ReST is simple, language & platform independent and Standard HTTP based mechanism that can be used through the Firewalls also.
Following are few simple examples of Get & POST upon ReST –
Example 1 :
- Request: (URL – http://abc.com/)
GET /
Accept: application/json+userdb - Response :
200 OK
Content-Type: application/json+userdb
{
"version": "1.0",
"links": [
{
"href": "/category",
"rel": "list",
"method": "GET"
},
{
"href": "/category",
"rel": "create",
"method": "POST"
}
]
}
Example 2 :
- Request : (URL – http://abc.com/category)
GET /category
Accept: application/json+userdb - Response :
200 OK
Content-Type: application/json+userdb
{
"categories": [
{
"categoryid": 1,
"categoryname": "Mobile",
"links": [
{
"href": "/category/1","rel": "self","method": "GET"
},
{
"href": "/category/1",
"rel": "edit",
"method": "PUT"
},
{
"href": "/category/1",
"rel": "delete",
"method": "DELETE"
}
]
},
{
"categoryid": 2,
"categoryname": "Tablet",
"links": [
{
"href": "/category/2",
"rel": "self",
"method": "GET"
},
{
"href": "/category/2",
"rel": "edit",
"method": "PUT"
},
{
"href": "/category/2",
"rel": "delete",
"method": "DELETE"
}
]
}
],
"links": [
{
"href": "/category",
"rel": "create",
"method": "POST"
}
]
}
Example 3:
- Request : (URL – http://abc.com/category)
POST /category
Accept: application/json+userdb
Content-Type: application/json+userdb
{
"categoryname": "Laptops"
} - Response :
201 Created
Content-Type: application/json+userdb
{
"category": {
"categoryid": 3,
"categoryname": "Laptops",
"links": [
{
"href": "/category/3",
"rel": "self",
"method": "GET"
},
{
"href": "/category/3",
"rel": "edit",
"method": "PUT"
},
{
"href": "/category/3",
"rel": "delete",
"method": "DELETE"
}
]
},
"links": {
"href": "/category",
"rel": "list",
"method": "GET"
}
} - http://www.csharptutorial.in/296/wcf-tutorials-soap-vs-rest-web-services-or-difference-between-soap-and-rest-web-services
