1. EEDC
34330
Execution
Environments for REST or SOAP?
Distributed
Computing
Master in Computer Architecture,
Networks and Systems - CANS
Homework number: 2
Josep Subirats Castell
(josep.subirats@bsc.es)

2. Table of Contents
 Advantages of REST over SOAP
 Disadvantages of REST over SOAP
 So, REST or SOAP?
2

3. Advantages of REST over SOAP (1/2)
 It uses the URI as interface and uses HTTP methods.
– SOAP requires specific knowledge of a new XML specification.
 Simpler client side: only HTTP is required to access
a REST WS.
– SOAP requires the use of a specific toolkit libraries to form
requests and parse the results.
 Requests and responses can be short (less traffic).
– SOAP requires an XML wrapper in each request and response.
3

4. Advantages of REST over SOAP (2/2)
 Its messages’ intent can be known by looking at the
used HTTP method in the request.
– SOAP always uses POST. Its Envelope must be examined (time
consuming) to know if it is meant to create/destroy data.
 No need to worry about authentication and
authorization: web servers take care of these tasks.
– SOAP places this burden to the application developer.
 Easier to test: only a browser is needed to generate
requests and visualize the responses.
4

5. Disadvantages of REST over SOAP
 In REST, data types are not known ahead of time.
– A WSDL file can be writen defining input/output parameters/data.
 SOAP is better when using attachments: it can
transport big texts and binaries easily.
– But it’s still easier and quicker when plain text strings
 Increased server complexity: some methods may
require serialization of the output to XML.
– (De)Serialization is handed by the SOAP server library.
5

6. So, REST or SOAP?
 REST is easier to build and lightweight.
 REST servers harder to implement than SOAP.
 REST clients simpler to implement than SOAP.
 When hosting Web Services, it’s the client side
complexity what matters most in attracting clients to
use your Web Service.
6

7. Questions?
7