Presentation for EEDC course. EMDC, FIB UPC

1. Why use SOAP when you
can REST?
Emmanouil Dimogerontakis, emmanouil.dimogerontakis@est.upc.fib.edu

2. WEB RESTs
REST is the key architectural principle of WEB
Roy T. Fielding. “A little REST and Relaxation.” ApacheCon Europe, 10 April 2008

3. REST is CRUD
So what?

4. The truth about the world!
● There are no applications you can think of
which cannot be made to fit into the GET /
PUT / POST /DELETE resources /
representations model of the world!
● Other interfaces considered harmful
because they increase the costs of
consuming particular service

5. What REST offers?
● Unlike SOAP and XML-RPC, REST does not
require a new message format
● Easy to build - no toolkits required
● Lightweight
● Human Readable Results

6. What the rest of the architectures
offer?
● Break Web architecture
● Significantly higher coordination costs
● Don't scale well

7. REST - the trendy way to build WEB
services
John Musser, Open APIs and the Semantic Web,Semtech 2011

8. RESTful Web Services

9. The Future is here
Vision:
A World Wide Web that runs on one set of
servers, uses one set of protocols, and obeys
one set of design principles
How:
Resource Oriented Architecture(ROA)
through REST.

10. So it is time to ... REST