Using REST for SOA Stefan Tilkov, QCon SF 2010

Size: px

Start display at page:

Download "Using REST for SOA Stefan Tilkov, QCon SF 2010"

Peregrine Freeman
6 years ago
Views:

1 Using REST for SOA Stefan Tilkov, QCon SF 2010

2 Stefan Tilkov innoq Deutschland GmbH innoq Schweiz GmbH Halskestraße 17 Gewerbestrasse 11 D Ratingen CH-6330 Cham Phone Phone

3 REST

4 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages

5 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages

6 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages

7 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages

8 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages GET /customers/1234 Host: example.com Accept: application/vnd.mycompany.customer+xml <customer>...</customer>

9 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages GET /customers/1234 Host: example.com Accept: application/vnd.mycompany.customer+xml <customer>...</customer> GET /customers/1234 Host: example.com Accept: text/x-vcard begin:vcard... end:vcard

10 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages

11 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages <order self=' <item> <amount>23</amount> <product ref=' /> </item> <customer ref=' /> <link rel='items' ref=' /> </order>

12 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages <order self=' <item> <amount>23</amount> <product ref=' /> </item> <customer ref=' /> <link rel='items' ref=' /> </order>

The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages <order

13 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages <order self=' <item> <amount>23</amount> <product ref=' /> </item> Stop Worrying <customer ref=' /> <link rel='items' About URI Design ref=' /> </order>

14 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages

15 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages GET /service/customers/1234 HTTP 1.1 Host: User-Agent: XYZ 1.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Keep-Alive: 300 Connection: keep-alive If-Modified-Since: Fri, 02 Oct :47:31 GMT If-None-Match: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=60

16 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages GET /service/customers/1234 HTTP 1.1 Host: User-Agent: XYZ 1.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Keep-Alive: 300 Connection: keep-alive If-Modified-Since: Fri, 02 Oct :47:31 GMT If-None-Match: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=60 HTTP/ OK Date: Sun, 04 Oct :36:25 GMT Server: Apache/ (Debian) Last-Modified: Fri, 02 Oct :47:31 GMT Etag: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=300 Accept-Ranges: bytes Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 7160 Keep-Alive: timeout=15, max=91 Connection: Keep-Alive Content-Type: application/xml <?xml version= 1.0 encoding= utf-8?>...

17 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages Standard Method GET /service/customers/1234 HTTP 1.1 Host: User-Agent: XYZ 1.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Keep-Alive: 300 Connection: keep-alive If-Modified-Since: Fri, 02 Oct :47:31 GMT If-None-Match: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=60 HTTP/ OK Date: Sun, 04 Oct :36:25 GMT Server: Apache/ (Debian) Last-Modified: Fri, 02 Oct :47:31 GMT Etag: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=300 Accept-Ranges: bytes Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 7160 Keep-Alive: timeout=15, max=91 Connection: Keep-Alive Content-Type: application/xml <?xml version= 1.0 encoding= utf-8?>...

18 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages Standard Method Media Type GET /service/customers/1234 HTTP 1.1 Host: User-Agent: XYZ 1.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Keep-Alive: 300 Connection: keep-alive If-Modified-Since: Fri, 02 Oct :47:31 GMT If-None-Match: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=60 HTTP/ OK Date: Sun, 04 Oct :36:25 GMT Server: Apache/ (Debian) Last-Modified: Fri, 02 Oct :47:31 GMT Etag: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=300 Accept-Ranges: bytes Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 7160 Keep-Alive: timeout=15, max=91 Connection: Keep-Alive Content-Type: application/xml <?xml version= 1.0 encoding= utf-8?>...

19 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages Standard Method GET /service/customers/1234 HTTP 1.1 Host: User-Agent: XYZ 1.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Keep-Alive: 300 Connection: keep-alive If-Modified-Since: Fri, 02 Oct :47:31 GMT If-None-Match: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=60 Media Type HTTP/ OK Date: Sun, 04 Oct :36:25 GMT Server: Apache/ (Debian) Last-Modified: Fri, 02 Oct :47:31 GMT Etag: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=300 Accept-Ranges: bytes Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 7160 Keep-Alive: timeout=15, max=91 Connection: Keep-Alive Content-Type: application/xml <?xml version= 1.0 encoding= utf-8?>... Data

20 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages Standard Method GET /service/customers/1234 HTTP 1.1 Host: User-Agent: XYZ 1.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Keep-Alive: 300 Connection: keep-alive If-Modified-Since: Fri, 02 Oct :47:31 GMT If-None-Match: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=60 Media Type HTTP/ OK Date: Sun, 04 Oct :36:25 GMT Server: Apache/ (Debian) Last-Modified: Fri, 02 Oct :47:31 GMT Etag: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=300 Accept-Ranges: bytes Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 7160 Keep-Alive: timeout=15, max=91 Connection: Keep-Alive Content-Type: application/xml <?xml version= 1.0 encoding= utf-8?>... Data Control Data

21 The REST Uniform Interface identification of resources resource manipulation through representations hypermedia as the engine of application state self-descriptive messages Standard Method Media Type GET /service/customers/1234 HTTP 1.1 Host: User-Agent: XYZ 1.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Keep-Alive: 300 Connection: keep-alive If-Modified-Since: Fri, 02 Oct :47:31 GMT If-None-Match: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=60 HTTP/ OK Date: Sun, 04 Oct :36:25 GMT Server: Apache/ (Debian) Last-Modified: Fri, 02 Oct :47:31 GMT Etag: "600028c-59fb-474f6852c9dab" Cache-Control: max-age=300 Accept-Ranges: bytes Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 7160 Keep-Alive: timeout=15, max=91 Connection: Keep-Alive Content-Type: application/xml VisibilityControl Data Data <?xml version= 1.0 encoding= utf-8?>...

22 getorderdetails() submitapplicationdata() updatequote() findmatchingbid() initiateprocess() cancelsubscription() listauctions() getusers()

23 getorderdetails() findmatchingbid() initiateprocess() submitapplicationdata() listauctions() getusers() updatequote() cancelsubscription()

24 getorderdetails() findmatchingbid() initiateprocess() submitapplicationdata() listauctions() getusers() updatequote() cancelsubscription()

25 getorderdetails() findmatchingbid() GET listauctions() initiateprocess() submitapplicationdata() POST getusers() PUT DELETE updatequote() cancelsubscription()

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

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

28 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) }... }

29 interface Resource { Resource(URI u) Response get() Response post(request r) Response put(request r) Response delete() } Any HTTP client (Firefox, IE, curl, wget) class CustomerCollection : Resource {... Response post(request r) { id = createcustomer(r) return new Response(201, r) }... }

30 interface Resource { Resource(URI u) Response get() Response post(request r) Response put(request r) Response delete() } Any HTTP client (Firefox, IE, curl, wget) Any HTTP server class CustomerCollection : Resource {... Response post(request r) { id = createcustomer(r) return new Response(201, r) }... }

31 interface Resource { Resource(URI u) Response get() Response post(request r) Response put(request r) Response delete() } Any HTTP client (Firefox, IE, curl, wget) Any HTTP server Caches class CustomerCollection : Resource {... Response post(request r) { id = createcustomer(r) return new Response(201, r) }... }

32 interface Resource { Resource(URI u) Response get() Response post(request r) Response put(request r) Response delete() } Any HTTP client (Firefox, IE, curl, wget) Any HTTP server Caches Proxies class CustomerCollection : Resource {... Response post(request r) { id = createcustomer(r) return new Response(201, r) }... }

33 interface Resource { Resource(URI u) Response get() Response post(request r) Response put(request r) Response delete() } Any HTTP client (Firefox, IE, curl, wget) Any HTTP server Caches Proxies Google, Yahoo!, MSN class CustomerCollection : Resource {... Response post(request r) { id = createcustomer(r) return new Response(201, r) }... }

34 interface Resource { Resource(URI u) Response get() Response post(request r) Response put(request r) Response delete() } Any HTTP client (Firefox, IE, curl, wget) Any HTTP server Caches Proxies Google, Yahoo!, MSN class CustomerCollection : Resource {... Response post(request r) { id = createcustomer(r) return new Response(201, r) }... } Anything that knows your app

35 interface Resource { Resource(URI u) Response get() Response post(request r) Response put(request r) Response delete() } Any HTTP client (Firefox, IE, curl, wget) Any HTTP server Caches Proxies Google, Yahoo!, MSN class CustomerCollection : Resource {... Response post(request r) { id = createcustomer(r) return new Response(201, r) }... } Anything that knows your app

36 interface Resource { Resource(URI u) Response get() Response post(request r) Response put(request r) Response delete() } generic Any HTTP client (Firefox, IE, curl, wget) Any HTTP server Caches Proxies Google, Yahoo!, MSN class CustomerCollection : Resource {... Response post(request r) { id = createcustomer(r) return new Response(201, r) }... } Anything that knows your app

37 interface Resource { Resource(URI u) Response get() Response post(request r) Response put(request r) Response delete() } generic Any HTTP client (Firefox, IE, curl, wget) Any HTTP server Caches Proxies Google, Yahoo!, MSN class CustomerCollection : Resource {... Response post(request r) { id = createcustomer(r) return new Response(201, r) }... } Anything that knows your app specific

38 Mapping Examples

39 Mapping Examples getfreetimeslots(person)

40 Mapping Examples getfreetimeslots(person) GET /people/{id}/timeslots?state=free

41 Mapping Examples getfreetimeslots(person) rejectapplication(application) GET /people/{id}/timeslots?state=free POST /rejections <application> <reason>unsuitable for us!</reason>

42 Mapping Examples getfreetimeslots(person) rejectapplication(application) GET /people/{id}/timeslots?state=free POST /rejections <application> <reason>unsuitable for us!</reason>

43 Mapping Examples getfreetimeslots(person) rejectapplication(application) performtariffcalculation(data) GET /people/{id}/timeslots?state=free POST /rejections <application> <reason>unsuitable for us!</reason> POST /contracts Data Location: GET /contracts/4711/tariff Result

44 Mapping Examples getfreetimeslots(person) rejectapplication(application) performtariffcalculation(data) GET /people/{id}/timeslots?state=free POST /rejections <application> <reason>unsuitable for us!</reason> POST /contracts Data Location: GET /contracts/4711/tariff Result

45 Mapping Examples getfreetimeslots(person) rejectapplication(application) performtariffcalculation(data) shiporder(id) GET /people/{id}/timeslots?state=free POST /rejections <application> <reason>unsuitable for us!</reason> POST /contracts Data Location: GET /contracts/4711/tariff Result PUT /orders/0815/status <status>shipped</status>

46 Mapping Examples getfreetimeslots(person) rejectapplication(application) performtariffcalculation(data) shiporder(id) GET /people/{id}/timeslots?state=free POST /rejections <application> <reason>unsuitable for us!</reason> POST /contracts Data Location: GET /contracts/4711/tariff Result PUT /orders/0815/status <status>shipped</status>

47 Mapping Examples getfreetimeslots(person) rejectapplication(application) performtariffcalculation(data) shiporder(id) GET /people/{id}/timeslots?state=free POST /rejections <application> <reason>unsuitable for us!</reason> POST /contracts Data Location: GET /contracts/4711/tariff Result PUT /orders/0815/status <status>shipped</status> shiporder(id) [variation] POST /shipments Data Location:

48 Mapping Examples getfreetimeslots(person) rejectapplication(application) performtariffcalculation(data) shiporder(id) GET /people/{id}/timeslots?state=free POST /rejections <application> <reason>unsuitable for us!</reason> POST /contracts Data Location: GET /contracts/4711/tariff Result PUT /orders/0815/status <status>shipped</status> shiporder(id) [variation] POST /shipments Data Location:

49 SOA

50 Well-known architectural principles, applied at different scale

52 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.

54 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

55 Lesson Learned:

56 Don t write manifestos

57 unless you look like this

58 or this

59 Bad Stuff

60 Good Stuff

61 Monoliths

62 Monoliths Redundant data

63 Monoliths Redundant data Redundant logic

64 Monoliths Redundant data Redundant logic Resistance to change

65 Monoliths Redundant data Redundant logic Resistance to change Late integration

66 Monoliths Redundant data Redundant logic Resistance to change Late integration Vendor dependency

67 Monoliths Redundant data Redundant logic Resistance to change Late integration Vendor dependency Bad

68 Monoliths Loosely coupled modules Redundant data Redundant logic Resistance to change Late integration Vendor dependency Bad

69 Monoliths Redundant data Loosely coupled modules Localized data Redundant logic Resistance to change Late integration Vendor dependency Bad

70 Monoliths Redundant data Redundant logic Loosely coupled modules Localized data Single implementation Resistance to change Late integration Vendor dependency Bad

71 Monoliths Redundant data Redundant logic Resistance to change Loosely coupled modules Localized data Single implementation Flexibility Late integration Vendor dependency Bad

72 Monoliths Redundant data Redundant logic Resistance to change Late integration Loosely coupled modules Localized data Single implementation Flexibility Early interoperability Vendor dependency Bad

73 Monoliths Redundant data Redundant logic Resistance to change Late integration Vendor dependency Loosely coupled modules Localized data Single implementation Flexibility Early interoperability Reliance on standards Bad

74 Monoliths Redundant data Redundant logic Resistance to change Late integration Vendor dependency Loosely coupled modules Localized data Single implementation Flexibility Early interoperability Reliance on standards Bad Good

75 RESTful SOA?

76 The Web & SOA

77 The Web & SOA Standard protocols

78 The Web & SOA Standard protocols Standard formats

79 The Web & SOA Standard protocols Standard formats Library and tool support

80 The Web & SOA Standard protocols Standard formats Library and tool support Mature and useful intermediaries

81 The Web & SOA Standard protocols Standard formats Library and tool support Mature and useful intermediaries Support for loose coupling

82 The Web & SOA Standard protocols Standard formats Library and tool support Mature and useful intermediaries Support for loose coupling Wide availability and adoption

83 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

84 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

85 But what about...

86 Enterprisey Stuff?

87 Encapsulation

88 Service Interface Service Logic Business Rules Data Access Data

89 Service Interface Service Logic WSDL Operations SOAP WS-* XML Parameters Messages Business Rules Data Access Data

90 Service Interface Service Logic WSDL Operations SOAP WS-* XML Parameters Messages Business Rules Data Access Data Resources HTTP JSON XML Hypermedia Representations

91 Transactions

92 RESTful Service Interface

93 RESTful Service Interface Implementation

94 RESTful Service Interface Implementation DB

95 RESTful Service Interface Implementation Local Tx DB

96 RESTful Service Interface Implementation Local Tx DB RESTful Service Interface

97 RESTful Service Interface Implementation Local Tx DB RESTful Service Interface Implementation

98 RESTful Service Interface Implementation Local Tx DB RESTful Service Interface Implementation DB A

99 RESTful Service Interface Implementation Local Tx DB RESTful Service Interface Implementation DB A DB B

100 RESTful Service Interface Implementation Local Tx DB RESTful Service Interface Implementation DB A DB B MQ

101 RESTful Service Interface Implementation Local Tx DB RESTful Service Interface DB A Implementation Distrib Tx DB B MQ

102 RESTful Service Interface Implementation DB Tx across Local Tx services RESTful Service Interface DB A Implementation Distrib Tx DB B MQ

103 create new Tx resource augment state

104 create new Tx resource augment state POST /transactions Location: <status>in progress</status> POST /transactions/4711

105 create new Tx resource augment state POST /transactions Location: <status>in progress</status> POST /transactions/ data...

106 create new Tx resource augment state POST /transactions Location: <status>in progress</status> POST /transactions/ data...

107 create new Tx resource augment state POST /transactions Location: <status>in progress</status> POST /transactions/ data... get state GET /transactions/ data... <link rel= status >in progress</link>

108 create new Tx resource augment state POST /transactions Location: <status>in progress</status> POST /transactions/ data... get state GET /transactions/ data... <link rel= status >in progress</link>

109 create new Tx resource augment state POST /transactions Location: <status>in progress</status> POST /transactions/ data... get state commit GET /transactions/ data... <link rel= status >in progress</link> PUT /transactions/4711/status <status>committed</status>

110 create new Tx resource augment state POST /transactions Location: <status>in progress</status> POST /transactions/ data... get state commit GET /transactions/ data... <link rel= status >in progress</link> PUT /transactions/4711/status <status>committed</status>

111 Stateful Communication

112 Turn session state R1 Client 1 Server R1 R2 Rn Client 2 R2 State Client 1 State Client 2 Server State Representation

113 into client or resource state Client 1 C1 R1 C1 C1 Server C1 R1 R2 C2 C2 Rn Client 2 R2 C2 C2 State Client 1 State Client 2 Server State Representation

114 Reliable Messaging

115 Client Server

116 Consumer Server

117 Consumer Provider

118 Consumer Provider

119 Consumer Provider

120 Consumer Provider Success/ Error

121 Consumer Provider Success/ Error

122 Consumer Provider Success/ Error

123 Consumer Provider? Success/ Error

124 Consumer Provider? Success/ Error

125 Consumer Provider? Success/ Error Idempotent Retry

126 Consumer Provider GET, PUT, DELETE? Success/ Error Idempotent Retry

127 Consumer Provider GET, PUT, DELETE? 202 Accepted Success/ Error Idempotent Retry

128 Consumer Provider GET, PUT, DELETE? 202 Accepted Success/ Error Idempotent Retry Async Accepted

129 Notifications

130 Call Stack

131 Call Stack Process

132 Call Stack Process Assumed Success Probability: 99.9%

133 Distributed Call Stack

134 Distributed Call Stack Assumed Success Probability: 99.6%

135 Distributed Call Stack Assumed Success Probability: 99.6%

136 Distributed Call Stack Assumed Success Probability: 99.6% 98%?

137 Distributed Call Stack 90%? 98%? Assumed Success Probability: 99.6%

138 Order Management

139 Order Management Orders

140 Submit Order Order Management Orders

141 Submit Order Order Management Customer Management Orders Customers

142 Submit Order Order GET Customer XYZ Customer Management Management Orders Customers

143 Submit Order Order Management GET Customer XYZ Customer Management Orders Customers Customers

144 Submit Order Order Management GET Customer XYZ Customer Management Orders Customers <Customer Change> Customers

145 Submit Order Order Management GET Customer XYZ Customer Management Orders Customers <Customer Change> Customers

146 Submit Order Order Management GET Customer XYZ Customer Management Orders Customers <Customer Change> Customers Feed-based notification

147 Atom Model Feed id title updated 0 * Entry id title updated * Category Content Resource OutOfLine InlineText InlineXHTML InlineOther

148 Security

149 Transport-based encrypt communication channel protection while in transit fast, efficient, wide-spread not end-to-end not persistent

150 Transport-based encrypt communication channel protection while in transit fast, efficient, wide-spread not end-to-end not persistent Message-based encrypt/sign individual messages indefinite protection Slow, inefficient, scarcely used end-to-end persistent

151 Transport-based encrypt communication channel protection while in transit fast, efficient, wide-spread not end-to-end not persistent Message-based encrypt/sign individual messages indefinite protection Slow, inefficient, scarcely used end-to-end persistent SSL

152 Transport-based encrypt communication channel protection while in transit fast, efficient, wide-spread not end-to-end not persistent Message-based encrypt/sign individual messages indefinite protection Slow, inefficient, scarcely used end-to-end persistent SSL HTTPS

153 Transport-based encrypt communication channel protection while in transit fast, efficient, wide-spread not end-to-end not persistent Message-based encrypt/sign individual messages indefinite protection Slow, inefficient, scarcely used end-to-end persistent SSL HTTPS REST

154 Transport-based encrypt communication channel protection while in transit fast, efficient, wide-spread not end-to-end not persistent Message-based encrypt/sign individual messages indefinite protection Slow, inefficient, scarcely used end-to-end persistent SSL HTTPS REST WSS

155 Transport-based encrypt communication channel protection while in transit fast, efficient, wide-spread not end-to-end not persistent Message-based encrypt/sign individual messages indefinite protection Slow, inefficient, scarcely used end-to-end persistent SSL HTTPS REST WSS XML

156 Transport-based encrypt communication channel protection while in transit fast, efficient, wide-spread not end-to-end not persistent Message-based encrypt/sign individual messages indefinite protection Slow, inefficient, scarcely used end-to-end persistent SSL HTTPS REST WSS XML WS-*

157 HTTP Security

158 HTTP Security Extensible HTTP Authentication Mechanism

159 HTTP Security Extensible HTTP Authentication Mechanism HTTP + SSL + Basic Auth

160 HTTP Security Extensible HTTP Authentication Mechanism HTTP + SSL + Basic Auth OpenID

161 HTTP Security Extensible HTTP Authentication Mechanism HTTP + SSL + Basic Auth OpenID OAuth

162 HTTP Security Extensible HTTP Authentication Mechanism HTTP + SSL + Basic Auth OpenID OAuth HMAC

163 Mixing RESTful HTTP w/ WS-*

164 Disclaimer first

165 set of problems

166 RESTful HTTP set of problems

167 RESTful HTTP MoM set of problems

168 RESTful HTTP MoM RMI/DCOM/CORBA set of problems

169 Spaces RESTful HTTP MoM RMI/DCOM/CORBA set of problems

170 Actors Spaces RESTful HTTP MoM RMI/DCOM/CORBA set of problems

171 Actors Spaces RESTful HTTP MoM RMI/DCOM/CORBA set of problems

172 Actors Spaces RESTful HTTP MoM RMI/DCOM/CORBA set of problems SOAP/WSDL

173 The SOAP/WSDL Problem

174 The SOAP/WSDL Problem Each application is different

175 The SOAP/WSDL Problem Each application is different Each application requires its own protocol

176 The SOAP/WSDL Problem Each application is different Each application requires its own protocol Need to learn a new API every single time

177 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

178 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 Separation of application and metadata

179 Anatomy of a WSDL File XML Schema Message Definitions Operation Names, Input, Output Meaningless Legacy Address Info

180 Anatomy of a WSDL File 80% XML Schema Message Definitions Operation Names, Input, Output Meaningless Legacy Address Info

181 Anatomy of a WSDL File 80% XML Schema 2% Message Definitions Operation Names, Input, Output Meaningless Legacy Address Info

182 Anatomy of a WSDL File 80% XML Schema 2% Message Definitions 5% Operation Names, Input, Output Meaningless Legacy Address Info

183 Anatomy of a WSDL File 80% XML Schema 2% Message Definitions 5% Operation Names, Input, Output 10% Meaningless Legacy Address Info

184 Anatomy of a WSDL File 80% XML Schema 2% Message Definitions 5% Operation Names, Input, Output 10% Meaningless Legacy 3% Address Info

185 SOAP/WSDL RESTful HTTP XML Schema Message Definitions Operation Names, Input, Meaningless Legacy Address Info

186 SOAP/WSDL RESTful HTTP XML Schema XML Schema (If you care for it) Message Definitions Operation Names, Input, Meaningless Legacy Address Info

187 SOAP/WSDL RESTful HTTP XML Schema XML Schema (If you care for it) Message Definitions Operation Names, Input, GET, PUT, POST, DELETE Meaningless Legacy Address Info

188 SOAP/WSDL RESTful HTTP XML Schema XML Schema (If you care for it) Message Definitions Operation Names, Input, GET, PUT, POST, DELETE Meaningless Legacy Address Info URIs

189 SOAP/WSDL RESTful HTTP XML Schema XML Schema (If you care for it) Message Definitions Operation Names, Input, GET, PUT, POST, DELETE Meaningless Legacy Address Info URIs Informal Documentation (Word, PDF, HTML,...)

190 SOAP/WSDL RESTful HTTP XML Schema XML Schema (If you care for it) Message Definitions Operation Names, Input, GET, PUT, POST, DELETE Meaningless Legacy Address Info URIs Informal Documentation (Word, PDF, HTML,...) Informal Documentation (Word, PDF, HTML,...)

191 SOAP/WSDL RESTful HTTP XML Schema XML Schema (If you care for it) Message Definitions Operation Names, Input, GET, PUT, POST, DELETE Meaningless Legacy Address Info URIs Informal Documentation (Word, PDF, HTML,...) Hypermedia Informal Documentation (Word, PDF, HTML,...)

192

193 SOAP HTTP Endpoint

194 SOAP HTTP Endpoint Resource

195 Order Customer Fulfilment Shipment

196 Resource Order Customer Fulfilment Shipment

197 Resource Order Customer Fulfilment Shipment

198 Resource Order Fulfilment Customer SelfServiceUI Shipment ProfileEntry

199 Resource Order Fulfilment Customer SelfServiceUI Shipment ProfileEntry

200 Resource Order Fulfilment Customer SelfServiceUI Order Management Documentation Shipment ProfileEntry

201 Resource Order Fulfilment Customer SelfServiceUI Order Management Documentation Shipment ProfileEntry

202 Resource Order Fulfilment Customer SelfServiceUI Order Management Documentation Shipment ProfileEntry Resources All The Way Down

203 Resource Order Fulfilment Customer SelfServiceUI Order Management Documentation Shipment ProfileEntry Resources All The Way Down

204 Resource Order Fulfilment Customer SelfServiceUI Order Management Documentation Shipment ProfileEntry Resources All The Way Down

205 Resource Order Fulfilment Customer SelfServiceUI Order Management Documentation Shipment ProfileEntry Resources All The Way Down

206 EJB 1.x JDBC

207 EJB 1.x JDBC Enterprise-compliant

208 EJB 1.x JDBC Enterprise-compliant Complex

209 EJB 1.x JDBC Enterprise-compliant Complex Heavyweight

210 EJB 1.x JDBC Enterprise-compliant Complex Heavyweight Managed

211 EJB 1.x JDBC Enterprise-compliant Straightforward Complex Heavyweight Managed

212 EJB 1.x JDBC Enterprise-compliant Complex Straightforward Simple Heavyweight Managed

213 EJB 1.x JDBC Enterprise-compliant Complex Heavyweight Straightforward Simple Lightweight Managed

214 EJB 1.x JDBC Enterprise-compliant Complex Heavyweight Managed Straightforward Simple Lightweight Integrated

215 EJB 1.x JDBC Enterprise-compliant Complex Heavyweight Managed Straightforward Simple Lightweight Integrated SOAP

216 EJB 1.x JDBC Enterprise-compliant Complex Heavyweight Managed Straightforward Simple Lightweight Integrated SOAP Plain HTTP

217 SOAP Plain HTTP

218 SOAP Legacy Access Plain HTTP

219 SOAP Legacy Access Transactional API Plain HTTP

220 SOAP Legacy Access Transactional API Processing-centric Plain HTTP

221 SOAP Legacy Access Transactional API Processing-centric Secured messages Plain HTTP

222 SOAP Legacy Access Transactional API Processing-centric Secured messages Politically motivated Plain HTTP

223 SOAP Legacy Access Transactional API Processing-centric Secured messages Politically motivated Plain HTTP Web-related

224 SOAP Legacy Access Transactional API Processing-centric Secured messages Politically motivated Plain HTTP Web-related (Meta-)Data-centric

225 SOAP Legacy Access Transactional API Processing-centric Secured messages Politically motivated Plain HTTP Web-related (Meta-)Data-centric Document-oriented

226 SOAP Legacy Access Transactional API Processing-centric Secured messages Politically motivated Plain HTTP Web-related (Meta-)Data-centric Document-oriented Interoperable

227 SOAP Legacy Access Transactional API Processing-centric Secured messages Politically motivated Plain HTTP Web-related (Meta-)Data-centric Document-oriented Interoperable Scalable

228 Steps for introducing REST to a SOA Enterprise

229 #0: Convince Management

230

231

232

233

234 My Internet is bigger than your enterprise. Paraphrasing Dare Obasanjo, see

235

236 VersicherungX

237 #1: Ensure your Web apps are RESTful

238 #2: Expose machine-readable information via HTTP GET

239 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.

240 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

241 #3: Distribute notifications via Atom feeds

242 #4: Manage Your Metadata with RESTful HTTP

243 #5: Ship RESTful client libraries

244 #6: Adopt existing infrastructure

245 #7: Use WS-* for read/write interactions if politics or legacy force you

246 #8: Draw your own Conclusions Watching the Adoption of WS-* vs. RESTful HTTP

247 Q&A innoq Deutschland GmbH innoq Schweiz GmbH Halskestraße 17 Gewerbestrasse 11 D Ratingen CH-6330 Cham Phone Phone Stefan Phone:

Pragmatic SOA Beyond Buzzwords and Flamewars. Stefan Tilkov, -

Pragmatic SOA Beyond Buzzwords and Flamewars Stefan Tilkov, innoq @stilkov - http://www.innoq.com/blog/st/ 1 Some Claims 2 Some Recommendations 3 Claim: Application architecture is irrelevant for your