REST vs SOAP (EEDC course)

1. EEDC
REST vs SOAP
Sunday, March 04,
Juan Luis Pérez
2012

2. SOAP
 Simple Object Access Protocol.
 Is a protocol
 Exposes operations that represents logic
 Operations are ports WDSL.
EEDC – REST vs SOAP 4 March 2012 2

3. REST
 REpresentational State Transfer.
 Style of software architecture
 Developed in parallel with HTTP/1.1
 Each unique URL is a representation of some object.
EEDC – REST vs SOAP 4 March 2012 3

4. What people are using?
Reference: http://www.slideshare.net/cesare.pautasso/bpm-with-rest
EEDC – REST vs SOAP 4 March 2012 4

5. Why?
 Only HTTP:
 GET (read), PUT (update), DELETE, POST (catch all)
 Lightweight (not a lot of extra xml markup)
 Human Readable Results
 Easy to build (no toolkits required)
EEDC – REST vs SOAP 4 March 2012 5

6. SOAP?
 RPC style (XML-RPC)
 RPC usually fights the web with Complexity
 Sessions
 Large Controllers
 Query String Param mappers
 Form deserializers
Abstract away the network!
EEDC – REST vs SOAP 4 March 2012 6

7. SOAP always more
 Protocol Layering
REST SOAP
EEDC – REST vs SOAP 4 March 2012 7

8. More?
 REST exposes resources that represent data, while
SOAP exposes operations that represent logic
 REST emphasizes simple p2p communication over
HTTP, while SOAP emphasized loosely coupled
distributed messaging
 REST supports multiple data formats, while SOAP
encodes everything in XML with data attachments
 REST emphasises stateless communication while
SOAP supports stateless and stateful operations
EEDC – REST vs SOAP 4 March 2012 8

9. How to compare?
REST
Architectural
Style for
the Web
SOA
Middleware
Interoperability
Standards
EEDC – REST vs SOAP 4 March 2012 9