REST v SOAP - A few perspectives

In this article, we look at the major differences between SOAP and REST. OOPS.. actually, comparing the two is a little like comparing apples to oranges, as SOAP is a protocol format based on XML, whereas REST is an architectural approach.

You will Learn

  • What is REST?
  • What is SOAP?
  • How are REST and SOAP different?


This is the second article in a series of articles on REST APIs:


REST vs SOAP are not really comparable. REST is an architectural style. SOAP is a message exchange format.

Let’s compare the popular implementations of REST and SOAP styles.

  • RESTful Sample Implementation : JSON over HTTP
  • SOAP Sample Implementation : XML over SOAP over HTTP

At a high level, SOAP is about restrictions on your message structures while REST is an architectural approach focused on using HTTP Transport.

  • SOAP is particular about the Data Exchange Format. With SOAP, this is always SOAP-XML, which is an XML with envelope, header and body. Both the request and response should adhere to the SOAP structure.
  • REST is very particular about using HTTP as the transport protocol. It intends to make the best use of the features provided by HTTP - Request methods, Request headers, Response, Response headers etc.

Message interchange format

  • With SOAP, you use SOAP XML format for Request and Response
  • With REST, there is no such fixed format. You could exchange messages based on XML, JSON or any other convenient format. JSON is the most popular among the used formats.

Service Definitions

  • SOAP makes use of Web Service Definition Language (WSDL).
  • REST does not have a standard service definition language. Even though WADL was one of the first standards to be proposed, it is not very popular. Swagger or Open API is another popular approach.


  • SOAP does not place any restrictions on the kind of transport protocol. You could either use Web (which is HTTP), or MQ.
  • REST intends to make the best use of HTTP Transport Protocol

Ease of Implementation

RESTFful services are typically a lot easier to implement than SOAP based web services.

  • REST typically uses JSON, which is easier to parse and process. In addition to that, REST does not require you to have a service definition in place to provide a web service.
  • However with SOAP, you are needed to define your service using WSDL, and greater overhead is involved in processing and parsing the SOAP-XML messages.

Do check out our video on this:

image info


In this article, we broadly looked the differences between REST and SOAP.

10 Step Reference Courses

Image Image Image Image Image

in28Minutes is helping 300,000 Learners across the world reach their learning goals. Click here for the complete catalogue of 30 Courses.

Related Posts

Spring Boot Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. This resources will help you learn and gain expertise at Spring Boot.

Spring and Spring Boot Video Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. Here's a list of video tutorials and courses for you

Software Design - Separation Of Concerns - with examples

Software architects and programmers love having Seperation of Concerns. What is it? Why is it important? Let's get started.

Object Oriented Software Design - Solid Principles - with examples

Software design is typically complex. Object oriented design takes it to the next level. There are a number of design patterns and other stuff to be aware of. Can we make things simple? What are the goals to aim for when you are doing object oriented design? SOLID Principles is a great starting point for Object Oriented Design.

Software Design - Open Closed Principle - with examples

Open Closed Principle is one of the SOLID Principles. You want your code to be easily extended. How do you achieve it with minimum fuss? Let's get started.

Software Design - What is Dependency Inversion Principle?

Dependency Inversion Principle is one of the important SOLID Principles. Dependency Inversion Principle is implemented by one of the most popular Java frameworks - Spring. What is it all about? How does it help you design good applications?

Introduction to Four Principles Of Simple Design

With agile and extreme programming, the focus is on keeping your design simple. How do you keep your design simple? How do you decide whether your code is good enough?

Software Design - Single Responsibility Principle - with examples

For me, Single Responsibility Principle is the most important design principle. What is Single Responsibility Principle? How do you use it? How does it help with making your software better? Let's get started.

REST API Best Practices - With Design Examples from Java and Spring Web Services

Designing Great REST API is important to have great microservices. How do you design your REST API? What are the best practices?

Designing REST API - What is Code First Approach?

Designing Great REST API is important to have great microservices. Code First approach focuses on generating the contract from code. Is it the best possible approach?