When To Use SOAP And When REST

Java Track 3.2 - Long Talk Jazoon'11
Tuesday, 21 June 2011, 14:00-14:50, Arena 4

 



Marek Potociar

Oracle, United States of America

 

 

When To Use SOAP And When REST

This talk will show use cases for when and how to use either SOAP protocols or the REST architecture to build Java applications. It will also discuss interoperability with non-Java frameworks.

For each use case, it will show Java programming models from the JAX-WS and JAX-RS specifications. Where those specifications do not cover a feature (e.g., WS-Security) we will show examples from popular Java WS implementations (e.g., Metro, Jersey).

By the end of this talk the developer will know when to use SOAP or REST, will know which features within each model to use and the Java programming models for those features.

Outline
Use Case: Service Discovery and Automation SOAP: WSDL; BPEL REST: WADL

Use Case: Public “Cloud” APIs

SOAP: Amazon search

REST: many services

Use Case: Small Devices (e.g., limited memory/bandwidth)

SOAP: large framework footprint;

REST: small framework footprint; content negotiation

Use Case: Large Messages (e.g., medical images)

SOAP: MTOM

REST: content negotiation

Use Case: Stateful Services (e.g., shopping cart)

SOAP: WS-Addressing; SOAP/TCP

REST: application defined URI space

Use Case: Point-to-point Security (e.g., ecommerce)

SOAP: HTTPS

REST: HTTPS

Use Case: End-to-end Security (e.g., medical, finance)

SOAP: WS-Security & WS-SecureConversation

REST: at application level

Use Case: 3rd Party Identity (e.g., healthcare, B2B)

SOAP: WS-Trust; SAML

REST: at application level

Use Case: 3rd Party Access (e.g., social applications)

SOAP: at application level

REST: OAuth

Use Case: Intermittent Connectivity (e.g., battlefields)

SOAP: WS-ReliableMessaging

REST: at application level

Tuesday, 21 June 2011

Wednesday, 22 June 2011

Thursday, 23 June 2011

Platinum Sponsor

Gold Sponsor

Silver Sponsor

 

Rookie Sponsor

Partners

 

Host City


Co-organiser

 
Home