using rest for soa - qconsf.com · using rest for soa stefan tilkov, qcon sf 2010. copyright 2010...

Copyright 2010 innoQ Deutschland GmbH

Using REST for SOAStefan Tilkov, QCon SF 2010


Stefan [email protected]

http://www.innoq.com/blog/st/@stilkov

Web Services Standards Overview

Vers

ion

3.0*

· Fe

brua

ry 2

007

This

post

er is

not

to b

e re

prod

uced

or t

rans

mitt

ed in

any

form

or f

or a

ny p

urpo

se w

ithou

t the

exp

ress

per

miss

ion

of in

noQ

Deut

schl

and

GmbH

.Co

pyrig

ht ©

inno

Q De

utsc

hlan

d Gm

bH.

All R

ight

s Res

erve

d. T

he p

oste

r may

also

con

tain

refe

renc

es to

oth

er c

ompa

ny, o

rgan

isatio

n, b

rand

and

pro

duct

nam

es.

Thes

e co

mpa

ny, o

rgan

isatio

n, b

rand

and

pro

duct

nam

es a

re u

sed

here

in fo

r ide

ntifi

catio

npur

pose

s onl

y an

d m

ay b

e th

e tr

adem

arks

of t

heir

resp

ectiv

e ow

ners

.

InteroperabilityIssues

Basic Profile1.1

WS-IFinal Specification

Basic Profile1.2

WS-IWorking Group Draft

Basic Profile2.0


Basic Security Profile1.0

WS-IBoard Approval Draft

REL Token Profile1.0


SAML Token Profile1.0


Conformance Claim Attachment Mechanism

(CCAM)1.0


Reliable AsynchronousMessaging Profile (RAMP)

1.0WS-I

Working Draft

Attachments Profile1.0


Simple SOAPBinding Profile

1.0 · WS-IFinal Specification

Business Process ExecutionLanguage for Web Services 1.1(BPEL4WS) · 1.1 · BEA Systems, IBM,

Microsoft, SAP, Siebel SystemsOASIS-Standard

WS-Choreography ModelOverview1.0 · W3C

Working Draft

Web Service ChoreographyInterface (WSCI)

1.0 · W3CSun Microsystems, SAP, BEA Systems

and Intalio · Note

Business Process Specifications

Business Process ExecutionLanguage for Web Services 2.0

(BPEL4WS) · 2.0OASIS, BEA Systems, IBM, Microsoft,

SAP, Siebel Systems · Committee Draft

Business Process Management Language (BPML)

1.1BPMI.org

Final Draft

Web Service ChoreographyDescription Language (CDL4WS)

1.0W3C

Candidate Recommendation

XML Process Definition Language (XPDL)

2.0Final

WS-Policy1.5

W3CWorking Draft

WS-PolicyAssertions1.1

BEA Systems, IBM, Microsoft, SAP

Public Draft

Metadata Specifications

WS-PolicyAttachment1.2

W3CW3C Member Submission

WS-DiscoveryMicrosoft, BEA Systems, Canon,

Intel and webMethodsDraft

WS-MetadataExchange1.1

BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun

Microsystems and webMethodsPublic Draft

Universal Description,Discovery and Integration

(UDDI)3.0.2

OASISOASIS-Standard

Web Service DescriptionLanguage 2.0 SOAP Binding

2.0W3C · Working Draft

Web Service Description Language 2.0 Core

2.0W3C


Web Service DescriptionLanguage 1.1

1.1W3CNote

WS-Security1.1

OASISOASIS-Standard

WS-SecurityPolicy1.1

IBM, Microsoft, RSA Security, VeriSign

Public Draft

Security Specifications

WS-Security: SOAP Message Security

1.1OASIS

Public Review Draft

WS-Security: Username Token Profile

1.1OASIS

Public Review Draft

WS-Security:Kerberos Binding

1.0Microsoft, IBM, OASIS

Working Draft

WS-Federation1.0

IBM, Microsoft, BEA Systems, RSA Security, and VeriSign

Initial Draft

WS-Security: SAML Token Profile

1.1OASIS

Public Review Draft

WS-TrustBEA Systems, Computer Associates,

IBM, Layer 7 Technologies, Microsoft,Netegrity, Oblix, OpenNetwork, Ping

Identity Corp., Reactivity, RSASecurity, VeriSign and Westbridge

Technology · Initial Draft

WS-SecureConversationBEA Systems, Computer Associates,



Technology · Public Draft

WS-Security: X.509Certificate Token Profile

1.1OASIS

Public Review Draft

WS-ReliableMessaging1.1

OASISCommittee Draft

Reliability Specifications

WS-Reliable Messaging Policy Assertion (WS-RM Policy)

1.1OASIS

Committee Draft

WS-Reliability1.1

OASISOASIS-Standard

WS-Coordination1.1

OASISWorking Draft

WS-Business Activity1.1

OASISWorking Draft

WS-Atomic Transaction1.1


WS-Composite ApplicationFramework (WS-CAF)

1.0 · ArjunaTechnologies, Fujitsu, IONA, Oracleand Sun Microsyst. · Committee Specification

WS-Context (WS-CTX)1.0 · Arjuna Technologies, Fujitsu,

IONA, Oracle and SunMicrosystems · Committee Draft

TransactionSpecifications

ResourceSpecifications

Management Using Web Services (WSDM-MUWS)

1.0OASIS

OASIS-Standard

Management Of Web Services (WSDM-MOWS)

1.0OASIS

OASIS-Standard

Management Specifications

WS-ManagementAMD, Dell, Intel, Microsoft and Sun

MicrosystemsPublished Specification

Service Modeling LanguageIBM, BEA, BMC, Cisco,

Dell, HP, Intel, Microsoft, SunDraft Specification

Web Services for Remote Portlets (WSRP)

2.0OASIS

Committee Draft

PresentationSpecifications

Web Services Resource Framework (WSRF)

1.2 · OASIS · OASIS-Standard

WS-BaseFaults (WSRF)1.2

OASISWorking Draft

WS-ServiceGroup (WSRF)1.2

OASISWorking Draft

WS-ResourceProperties1.2

OASISWorking Draft

WS-ResourceLifetime1.2

OASISWorking Draft

WS-TransferW3C

W3C Member Submission

Resource RepresentationSOAP Header Block (RRSHB)

W3C · Recommendation

WS-Coordination Framework (WS-CF)

1.0 · ArjunaTechnologies, Fujitsu, IONA, Oracleand Sun Microsystems · Committee Draft

WS-Transaction Management (WS-TXM)


innoQ Deutschland GmbH innoQ Schweiz GmbHHalskestraße 17 Gewerbestrasse 11D-40880 Ratingen CH-6330 ChamPhone +49 2102 77162-100 Phone +41 41 743 [email protected] · www.innoq.com

SOAP Message Transmission Optimization

Mechanism (MTOM)1.0 · W3C

Recommendation

SOAP1.2

W3CRecommendation

SOAP1.1

W3CNote

WS-Addressing – Core1.0

W3CRecommendation

WS-EventingW3C

Public Draft

WS-Addressing – WSDLBinding

1.0W3C


WS-Addressing – SOAP Binding

1.0W3C

Recommendation

WS-EnumerationSystinet, Microsoft, Sonic Software,

BEA Systems and Computer Associates

Public Draft

WS-Notification1.3

OASISOASIS-Standard

WS-BaseNotification1.3

OASISOASIS-Standard

WS-Topics1.3

OASISOASIS-Standard

WS-BrokeredNotification1.3

OASISOASIS-Standard

XML 1.11.1

W3CRecommendation

XML 1.01.0

W3CRecommendation

Namespaces in XML1.1

W3CRecommendation

XML Information Set1.0

W3CRecommendation

XML Schema1.1

W3CWorking Draft

XML binary Optimized Packaging (XOP)

1.0W3C

Recommendation

Describing Media Content ofBinary Data in XML (DMCBDX)

W3CNote

XML Specifications

Messaging Specifications SOAP

*HINWEIS: Dies ist eineim Informationsgehalt reduzierte Version des WS-Standards-Posters voninnoQ. Sie finden die Vollversion zum Downloadim PDF-Format unter:www.innoq.com/resources/ws-standards-poster/.Dort können Sie auch dasausgedruckte Poster imDIN A0 Format bestellen.


REST


identificationof resources

resource manipulation through representations

hypermedia as the engine of application state

self-descriptive messages

The REST Uniform Interface


The REST Uniform Interfaceidentificationof resources






http://example.com/orders?year=2008

http://example.com/customers/1234

http://example.com/orders/2007/10/776654

http://example.com/products/4554

http://example.com/processes/sal-increase-234







GET /customers/1234Host: example.comAccept: application/vnd.mycompany.customer+xml

<customer>...</customer>







GET /customers/1234Host: example.comAccept: application/vnd.mycompany.customer+xml

<customer>...</customer>

GET /customers/1234Host: example.comAccept: text/x-vcard

begin:vcard...end:vcard







<order self='http://example.org/0E6C2BC1094C'> <item> <amount>23</amount> <product ref='http://amazon.com/products/A31138B3' /> </item> <customer ref='http://example.net/4E8F-891D' /> <link rel='items' ref='http://example.com/EFDBE4A38931' /></order>





Stop WorryingAbout URI Design






GET /service/customers/1234 HTTP 1.1Host: www.example.comUser-Agent: XYZ 1.1Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8Keep-Alive: 300Connection: keep-aliveIf-Modified-Since: Fri, 02 Oct 2009 16:47:31 GMTIf-None-Match: "600028c-59fb-474f6852c9dab"Cache-Control: max-age=60

http://www.example.com








HTTP/1.1 200 OKDate: Sun, 04 Oct 2009 19:36:25 GMTServer: Apache/2.2.11 (Debian)Last-Modified: Fri, 02 Oct 2009 16:47:31 GMTEtag: "600028c-59fb-474f6852c9dab"Cache-Control: max-age=300Accept-Ranges: bytesVary: Accept-EncodingContent-Encoding: gzipContent-Length: 7160Keep-Alive: timeout=15, max=91Connection: Keep-AliveContent-Type: application/xml

<?xml version=‘1.0’ encoding=‘utf-8’ ?>...











StandardMethod











StandardMethod

Media Type











StandardMethod

Media Type

Data











StandardMethod

Media Type

Data

Control Data











StandardMethod

Media Type

Data

Control DataVisibility


getOrderDetails()

updateQuote()

cancelSubscription()

findMatchingBid()

initiateProcess()

submitApplicationData()

listAuctions()

getUsers()


getOrderDetails()

updateQuote() cancelSubscription()

findMatchingBid()

initiateProcess()


listAuctions()

getUsers()


getOrderDetails()

updateQuote() cancelSubscription()

findMatchingBid()

initiateProcess()


listAuctions()

getUsers()

GET

PUT

POST

DELETE


interface Resource { Resource(URI u) Response get() Response post(Request r) Response put(Request r) Response delete()}



class CustomerCollection : Resource { ... Response post(Request r) { id = createCustomer(r) return new Response(201, r) } ...}




Any HTTP client(Firefox, IE, curl, wget)





Any HTTP server





Any HTTP server

Caches





Any HTTP server

Caches

Proxies





Any HTTP server

Caches

Proxies

Google, Yahoo!, MSN





Any HTTP server

Caches

Proxies

Google, Yahoo!, MSN

Anything that knows your app



generic



Any HTTP server

Caches

Proxies

Google, Yahoo!, MSN




generic

specific



Any HTTP server

Caches

Proxies

Google, Yahoo!, MSN



Mapping Examples


Mapping ExamplesgetFreeTimeSlots(Person) →GET /people/{id}/timeslots?state=free

rejectApplication(Application) →POST /rejections↵ <application>http://...</application>↵ <reason>Unsuitable for us!</reason>

performTariffCalculation(Data) →POST /contracts↵ Data←Location: http://.../contracts/4711→GET /contracts/4711/tariff←Result

shipOrder(ID) →PUT /orders/0815/status↵ <status>shipped</status>

shipOrder(ID) [variation] →POST /shipments↵ Data←Location: http://.../shipments/4711


SOA


Well-known architectural principles, applied at different

scale


http://soa-manifesto.org/


Through our work we have come to prioritize:

Business value over technical strategy Strategic goals over project-specific benefits

Intrinsic interoperability over custom integration Shared services over specific-purpose implementations

Flexibility over optimization Evolutionary refinement over pursuit of initial perfection

That is, while we value the items on the right, we value the items on the left more.


“Unlike the Agile manifesto however, the SOA manifesto is nothing more than snake oil to give the vendor community a thin veneer of respectability atop their increasing bureaucracy, deteriorating levels of innovation, and increasingly painful pricing models.”

– Jim Webber

http://jim.webber.name/2009/10/24/95bf2681-9a7a-4f94-94d6-2156a3a46411.aspx


Lesson Learned:


Don’t write manifestos …


… unless you look like this


… or this


Bad Stuff


Good Stuff


Monoliths


Monoliths

Redundant data


Monoliths

Redundant data

Redundant logic


Monoliths

Redundant data

Redundant logic

Resistance to change


Monoliths

Redundant data

Redundant logic


Late integration


Monoliths

Redundant data

Redundant logic


Late integration

Vendor dependency


Monoliths

Redundant data

Redundant logic


Late integration

Vendor dependency

Bad


Monoliths

Redundant data

Redundant logic


Late integration

Vendor dependency

Bad

Loosely coupled modules


Monoliths

Redundant data

Redundant logic


Late integration

Vendor dependency

Bad


Localized data


Monoliths

Redundant data

Redundant logic


Late integration

Vendor dependency

Bad


Localized data

Single implementation


Monoliths

Redundant data

Redundant logic


Late integration

Vendor dependency

Bad


Localized data


Flexibility


Monoliths

Redundant data

Redundant logic


Late integration

Vendor dependency

Bad


Localized data


Flexibility

Early interoperability


Monoliths

Redundant data

Redundant logic


Late integration

Vendor dependency

Bad


Localized data


Flexibility


Reliance on standards


Monoliths

Redundant data

Redundant logic


Late integration

Vendor dependency

Bad


Localized data


Flexibility


Reliance on standards

Good


RESTful SOA?


The Web & SOA


The Web & SOA

Standard protocols

Standard formats

Library and tool support

Mature and useful intermediaries

Support for loose coupling

Wide availability and adoption

Well-defined architectural model


The Web & SOA

Standard protocols ✔

Standard formats ✔

Library and tool support ✔

Mature and useful intermediaries ✔

Support for loose coupling ✔

Wide availability and adoption ✔

Well-defined architectural model ✔


But what about ...


“Enterprisey” Stuff?


Encapsulation


Data

Data Access

Business Rules

Service Logic

Service Interface


Data

Data Access

Business Rules

Service Logic

Service Interface

WSDLSOAP WS-* XML

Operations

Parameters

Messages


Data

Data Access

Business Rules

Service Logic

Service Interface

WSDLSOAP WS-* XML

Operations

Parameters

Messages

HTTPJSON XML

Resources

Hypermedia

Representations


Transactions


RESTful Service

Interface


RESTful Service

InterfaceImplementation


DBRESTful Service



DBRESTful Service


Local Tx


DBRESTful Service


Local Tx

RESTful Service

Interface


DBRESTful Service


Local Tx

RESTful Service



DBRESTful Service


Local Tx

DB ARESTful Service



DBRESTful Service


Local Tx

DB ARESTful Service


DB B


DBRESTful Service


Local Tx

DB ARESTful Service


DB B

MQ


DBRESTful Service


Local Tx

DB ARESTful Service


DB B

MQ

Distrib Tx


DBRESTful Service


Local Tx

DB ARESTful Service


DB B

MQ

Distrib Tx

Tx across services


create new Tx resource →POST /transactions←Location: http://.../transactions/4711<status>in progress</status>

augment state →POST /transactions/4711 ↵ ...data...

get state →GET /transactions/4711←... data ...↵<link rel=‘status’>in progress</link>

commit →PUT /transactions/4711/status↵ <status>committed</status>


Stateful Communication


Server

Client 1

Client 2State Client 1

State Client 2

Server State

R1R2

Rn

Representation

R1

R2

Turn session state …


Server

Client 1

C1 C1

Client 2

C2

State Client 1

State Client 2

Server State

Representation

R1 R2

RnC2

C2

C2

C1C1

R2

R1

… into client or resource state


Reliable Messaging


Client Server


ServerConsumer


Consumer Provider


Consumer Provider

Success/Error


Consumer Provider

?

Success/Error


Consumer Provider

?

Success/Error

IdempotentRetry


Consumer Provider

?

Success/Error

IdempotentRetry

GET, PUT, DELETE


Consumer Provider

?

Success/Error

IdempotentRetry

GET, PUT, DELETE

202 Accepted


Consumer Provider

?

Success/Error

IdempotentRetry

AsyncAccepted

GET, PUT, DELETE

202 Accepted


Notifications


Call Stack


Process

Call Stack


Process

Call Stack

Assumed Success Probability: 99.9%


Distributed Call Stack



Assumed Success Probability: 99.6%



Assumed Success Probability: 99.6%98%?



Assumed Success Probability: 99.6%98%?90%?


Order Management


Order Management

Orders


Order Management

SubmitOrder

Orders


Order Management

SubmitOrder

Orders

CustomerManagement

Customers


Order Management

GET CustomerXYZ

SubmitOrder

Orders

CustomerManagement

Customers


Order Management

GET CustomerXYZ

SubmitOrder

Orders

CustomerManagement

CustomersCustomers


<CustomerChange>

Order Management

GET CustomerXYZ

SubmitOrder

Orders

CustomerManagement

CustomersCustomers


<CustomerChange>

Order Management

GET CustomerXYZ

SubmitOrder

Orders

CustomerManagement

CustomersCustomers

Feed-based notification


Atom Model

Feed Entry*0

idtitle

updated

idtitle

updated

Content

InlineXHTMLInlineTextOutOfLineResource InlineOther

Category*


Security


Transport-based

encrypt communication channelprotection while in transitfast, efficient, wide-spreadnot end-to-endnot persistent


Message-based

encrypt/sign individual messagesindefinite protectionSlow, inefficient, scarcely usedend-to-endpersistent

Transport-based



Message-based


Transport-based


SSL


Message-based


Transport-based


SSLHTTPS


Message-based


Transport-based


SSLHTTPSREST


Message-based


Transport-based


SSLHTTPSREST

WSS


Message-based


Transport-based


SSLHTTPSREST

WSSXML


Message-based


Transport-based


SSLHTTPSREST

WSSXMLWS-*


HTTP Security


HTTP Security

Extensible HTTP Authentication Mechanism


HTTP Security


HTTP + SSL + Basic Auth


HTTP Security



OpenID


HTTP Security



OpenID

OAuth


HTTP Security



OpenID

OAuth

HMAC


Mixing RESTful HTTP w/ WS-*


Disclaimer first


set of problems


RESTful HTTP

set of problems


RESTful HTTP

set of problems

MoM


RESTful HTTP

set of problems

MoM

RMI/DCOM/CORBA


RESTful HTTP

set of problems

MoM

RMI/DCOM/CORBA

Spaces


RESTful HTTP

set of problems

MoM

RMI/DCOM/CORBA

SpacesActors


RESTful HTTP

set of problems

MoM

RMI/DCOM/CORBA

SpacesActors

…


RESTful HTTP

set of problems

MoM

RMI/DCOM/CORBA

SOAP/WSDL

SpacesActors

…


The SOAP/WSDL Problem



Each application is different




Each application requires its own protocol





Need to learn a new API every single time






WSDL as formal approach for syntax only






WSDL as formal approach for syntax only

Separation of application and metadata


XML Schema

Anatomy of a WSDL File

Message Definitions

Address Info

Operation Names, Input, Output

Meaningless Legacy


XML Schema


Message Definitions

Address Info


Meaningless Legacy

80%


XML Schema


Message Definitions

Address Info


Meaningless Legacy

80%

2%


XML Schema


Message Definitions

Address Info


Meaningless Legacy

80%

2%

5%


XML Schema


Message Definitions

Address Info


Meaningless Legacy

80%

2%

5%

10%


XML Schema


Message Definitions

Address Info


Meaningless Legacy

80%

2%

3%

5%

10%


SOAP/WSDL

XML Schema

Message Definitions

Address Info

Operation Names, Input,

Meaningless Legacy

RESTful HTTP


SOAP/WSDL

XML Schema

Message Definitions

Address Info


Meaningless Legacy

RESTful HTTPXML Schema

(If you care for it)


SOAP/WSDL

XML Schema

Message Definitions

Address Info


Meaningless Legacy

RESTful HTTP

GET, PUT, POST, DELETE

XML Schema(If you care for it)


SOAP/WSDL

XML Schema

Message Definitions

Address Info


Meaningless Legacy

RESTful HTTP

URIs




SOAP/WSDL

XML Schema

Message Definitions

Address Info


Meaningless Legacy

RESTful HTTP

URIs


“Informal” Documentation(Word, PDF, HTML, ...)



SOAP/WSDL

XML Schema

Message Definitions

Address Info


Meaningless Legacy

RESTful HTTP

URIs






SOAP/WSDL

XML Schema

Message Definitions

Address Info


Meaningless Legacy

RESTful HTTP

URIs





Hypermedia


http://example.com/someService


SOAP HTTP “Endpoint”



SOAP HTTP “Endpoint”


Resource


Order

Shipment

Fulfilment

Customer


Order

Shipment

Fulfilment

Customer

Resource


Order

Shipment

Fulfilment

Customer

Resource

ProfileEntry

SelfServiceUI


Order

Shipment

Fulfilment

Customer

Resource

ProfileEntry

SelfServiceUI

Order Management

Documentation


Resources All The Way Down

Order

Shipment

Fulfilment

Customer

Resource

ProfileEntry

SelfServiceUI

Order Management

Documentation


JDBCEJB 1.x


JDBCEJB 1.x

Enterprise-compliant


JDBCEJB 1.x


Complex


JDBCEJB 1.x


Complex

Heavyweight


JDBCEJB 1.x


Complex

Heavyweight

Managed


JDBCEJB 1.x


Complex

Heavyweight

Managed

Straightforward


JDBCEJB 1.x


Complex

Heavyweight

Managed

Straightforward

Simple


JDBCEJB 1.x


Complex

Heavyweight

Managed

Straightforward

Simple

Lightweight


JDBCEJB 1.x


Complex

Heavyweight

Managed

Straightforward

Simple

Lightweight

Integrated


JDBCEJB 1.x

SOAP


Complex

Heavyweight

Managed

Straightforward

Simple

Lightweight

Integrated


JDBCEJB 1.x

Plain HTTPSOAP


Complex

Heavyweight

Managed

Straightforward

Simple

Lightweight

Integrated


Plain HTTP

SOAP


Plain HTTP

SOAP Legacy Access


Plain HTTP

SOAP Legacy AccessTransactional API


Plain HTTP

SOAP Legacy AccessTransactional APIProcessing-centric


Plain HTTP

SOAP Legacy AccessTransactional APIProcessing-centricSecured messages


Plain HTTP

SOAP Legacy AccessTransactional APIProcessing-centricSecured messagesPolitically motivated


Plain HTTP


Web-related


Plain HTTP


Web-related(Meta-)Data-centric


Plain HTTP


Web-related(Meta-)Data-centricDocument-oriented


Plain HTTP


Web-related(Meta-)Data-centricDocument-orientedInteroperable


Plain HTTP


Web-related(Meta-)Data-centricDocument-orientedInteroperableScalable


Steps for introducing REST to a SOA Enterprise


#0: Convince Management


“My Internet is bigger than your enterprise.”

Paraphrasing Dare Obasanjo,see http://tinyurl.com/dare-enterprise


VersicherungX


#1: Ensure your Web apps are RESTful


#2: Expose machine-readable information

via HTTP GET


“I do think the REST-afarians are missing an opportunity by not driving home the secret sauce that is HTTP GET. […] GET is one

of the most optimized pieces of distributed systems plumbing in the world. It's an absolute/objective slam dunk. No arguing/evangelism needed IMO. GET is

the classic ‘the first bag is free’ kind of feature a platform builder dreams about.”


Don Box, Co-inventor of SOAP

“I do think the REST-afarians are missing an opportunity by not driving home the secret sauce that is HTTP GET. […] GET is one

of the most optimized pieces of distributed systems plumbing in the world. It's an absolute/objective slam dunk. No arguing/evangelism needed IMO. GET is

the classic ‘the first bag is free’ kind of feature a platform builder dreams about.”


#3: Distribute notifications via Atom feeds


#4: Manage Your Metadata with RESTful HTTP


#5: Ship RESTful client libraries


#6: Adopt existing infrastructure


#7: Use WS-* forread/write interactions if

politics or legacy force you


#8: Draw your own Conclusions Watching

the Adoptionof WS-* vs. RESTful HTTP


Q&A

Stefan Tilkov, @[email protected]://www.innoq.com/blog/st/Phone: +49 170 471 2625

Web Services Standards Overview

Vers

ion

3.0*

· Fe

brua

ry 2

007

This

post

er is

not

to b

e re

prod

uced

or t

rans

mitt

ed in

any

form

or f

or a

ny p

urpo

se w

ithou

t the

exp

ress

per

miss

ion

of in

noQ

Deut

schl

and

GmbH

.Co

pyrig

ht ©

inno

Q De

utsc

hlan

d Gm

bH.

All R

ight

s Res

erve

d. T

he p

oste

r may

also

con

tain

refe

renc

es to

oth

er c

ompa

ny, o

rgan

isatio

n, b

rand

and

pro

duct

nam

es.

Thes

e co

mpa

ny, o

rgan

isatio

n, b

rand

and

pro

duct

nam

es a

re u

sed

here

in fo

r ide

ntifi

catio

npur

pose

s onl

y an

d m

ay b

e th

e tr

adem

arks

of t

heir

resp

ectiv

e ow

ners

.

InteroperabilityIssues

Basic Profile1.1


Basic Profile1.2


Basic Profile2.0


Basic Security Profile1.0

WS-IBoard Approval Draft

REL Token Profile1.0


SAML Token Profile1.0


Conformance Claim Attachment Mechanism

(CCAM)1.0


Reliable AsynchronousMessaging Profile (RAMP)

1.0WS-I

Working Draft

Attachments Profile1.0


Simple SOAPBinding Profile

1.0 · WS-IFinal Specification

Business Process ExecutionLanguage for Web Services 1.1(BPEL4WS) · 1.1 · BEA Systems, IBM,

Microsoft, SAP, Siebel SystemsOASIS-Standard

WS-Choreography ModelOverview1.0 · W3C

Working Draft

Web Service ChoreographyInterface (WSCI)

1.0 · W3CSun Microsystems, SAP, BEA Systems

and Intalio · Note

Business Process Specifications

Business Process ExecutionLanguage for Web Services 2.0

(BPEL4WS) · 2.0OASIS, BEA Systems, IBM, Microsoft,

SAP, Siebel Systems · Committee Draft

Business Process Management Language (BPML)

1.1BPMI.org

Final Draft

Web Service ChoreographyDescription Language (CDL4WS)

1.0W3C


XML Process Definition Language (XPDL)

2.0Final

WS-Policy1.5

W3CWorking Draft

WS-PolicyAssertions1.1

BEA Systems, IBM, Microsoft, SAP

Public Draft

Metadata Specifications

WS-PolicyAttachment1.2

W3CW3C Member Submission

WS-DiscoveryMicrosoft, BEA Systems, Canon,

Intel and webMethodsDraft

WS-MetadataExchange1.1

BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun

Microsystems and webMethodsPublic Draft

Universal Description,Discovery and Integration

(UDDI)3.0.2

OASISOASIS-Standard

Web Service DescriptionLanguage 2.0 SOAP Binding

2.0W3C · Working Draft

Web Service Description Language 2.0 Core

2.0W3C


Web Service DescriptionLanguage 1.1

1.1W3CNote

WS-Security1.1

OASISOASIS-Standard

WS-SecurityPolicy1.1

IBM, Microsoft, RSA Security, VeriSign

Public Draft

Security Specifications

WS-Security: SOAP Message Security

1.1OASIS

Public Review Draft

WS-Security: Username Token Profile

1.1OASIS

Public Review Draft

WS-Security:Kerberos Binding

1.0Microsoft, IBM, OASIS

Working Draft

WS-Federation1.0

IBM, Microsoft, BEA Systems, RSA Security, and VeriSign

Initial Draft

WS-Security: SAML Token Profile

1.1OASIS

Public Review Draft

WS-TrustBEA Systems, Computer Associates,



Technology · Initial Draft

WS-SecureConversationBEA Systems, Computer Associates,



Technology · Public Draft

WS-Security: X.509Certificate Token Profile

1.1OASIS

Public Review Draft

WS-ReliableMessaging1.1


Reliability Specifications

WS-Reliable Messaging Policy Assertion (WS-RM Policy)

1.1OASIS

Committee Draft

WS-Reliability1.1

OASISOASIS-Standard

WS-Coordination1.1

OASISWorking Draft

WS-Business Activity1.1

OASISWorking Draft

WS-Atomic Transaction1.1


WS-Composite ApplicationFramework (WS-CAF)

1.0 · ArjunaTechnologies, Fujitsu, IONA, Oracleand Sun Microsyst. · Committee Specification

WS-Context (WS-CTX)1.0 · Arjuna Technologies, Fujitsu,

IONA, Oracle and SunMicrosystems · Committee Draft

TransactionSpecifications

ResourceSpecifications

Management Using Web Services (WSDM-MUWS)

1.0OASIS

OASIS-Standard

Management Of Web Services (WSDM-MOWS)

1.0OASIS

OASIS-Standard

Management Specifications

WS-ManagementAMD, Dell, Intel, Microsoft and Sun

MicrosystemsPublished Specification

Service Modeling LanguageIBM, BEA, BMC, Cisco,

Dell, HP, Intel, Microsoft, SunDraft Specification

Web Services for Remote Portlets (WSRP)

2.0OASIS

Committee Draft

PresentationSpecifications

Web Services Resource Framework (WSRF)

1.2 · OASIS · OASIS-Standard

WS-BaseFaults (WSRF)1.2

OASISWorking Draft

WS-ServiceGroup (WSRF)1.2

OASISWorking Draft

WS-ResourceProperties1.2

OASISWorking Draft

WS-ResourceLifetime1.2

OASISWorking Draft

WS-TransferW3C

W3C Member Submission

Resource RepresentationSOAP Header Block (RRSHB)

W3C · Recommendation

WS-Coordination Framework (WS-CF)


WS-Transaction Management (WS-TXM)


innoQ Deutschland GmbH innoQ Schweiz GmbHHalskestraße 17 Gewerbestrasse 11D-40880 Ratingen CH-6330 ChamPhone +49 2102 77162-100 Phone +41 41 743 [email protected] · www.innoq.com

SOAP Message Transmission Optimization

Mechanism (MTOM)1.0 · W3C

Recommendation

SOAP1.2

W3CRecommendation

SOAP1.1

W3CNote

WS-Addressing – Core1.0

W3CRecommendation

WS-EventingW3C

Public Draft

WS-Addressing – WSDLBinding

1.0W3C


WS-Addressing – SOAP Binding

1.0W3C

Recommendation

WS-EnumerationSystinet, Microsoft, Sonic Software,

BEA Systems and Computer Associates

Public Draft

WS-Notification1.3

OASISOASIS-Standard

WS-BaseNotification1.3

OASISOASIS-Standard

WS-Topics1.3

OASISOASIS-Standard

WS-BrokeredNotification1.3

OASISOASIS-Standard

XML 1.11.1

W3CRecommendation

XML 1.01.0

W3CRecommendation

Namespaces in XML1.1

W3CRecommendation

XML Information Set1.0

W3CRecommendation

XML Schema1.1

W3CWorking Draft

XML binary Optimized Packaging (XOP)

1.0W3C

Recommendation

Describing Media Content ofBinary Data in XML (DMCBDX)

W3CNote

XML Specifications

Messaging Specifications SOAP

*HINWEIS: Dies ist eineim Informationsgehalt reduzierte Version des WS-Standards-Posters voninnoQ. Sie finden die Vollversion zum Downloadim PDF-Format unter:www.innoq.com/resources/ws-standards-poster/.Dort können Sie auch dasausgedruckte Poster imDIN A0 Format bestellen.

mailto:[email protected]

mailto:[email protected]

http://www.innoq.com

http://www.innoq.com

using rest for soa - qconsf.com · using rest for soa stefan tilkov, qcon sf 2010. copyright 2010...

Documents