{"id":713,"date":"2005-03-12T01:20:00","date_gmt":"2005-03-12T05:20:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/2005\/03\/12\/udell-on-rest-and-soa\/"},"modified":"2005-03-12T01:20:00","modified_gmt":"2005-03-12T05:20:00","slug":"udell-on-rest-and-soa","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2005\/03\/udell-on-rest-and-soa\/","title":{"rendered":"Udell on REST and SOA"},"content":{"rendered":"<p><a href=\"\">Jon Udell urges<\/a> the REST movement to not dismiss SOA.\nSpecifically &#8230;<\/p>\n\n<blockquote>\nNow that the benefits of REST are abundantly clear, it&#8217;s time to circle back and ask when REST isn&#8217;t sufficient. The answer is that we&#8217;ll need the kinds of capabilities WS-* provides as our point-to-point, client\/server-like applications evolve into webs of communicating services.\n<\/blockquote>\n\n<p>Yes, absolutey, we&#8217;ll need the <em>capabilities<\/em> that the\nWS-* stack provides (for the most part).  But do we need the WS-* stack\nitself to provide those capabilities?  I&#8217;m certainly all for trying to reuse\nexisting specs where that makes sense.  The issue though, is that with\nmost of them, they explicitly or implicitly require disregarding\na key contraints of REST, disrespecting Web architecture, or both.\nWSDL&#8217;s probably the poster child for this, as its raison d&#8217;etre is\nprimarily to encourage rejection of REST&#8217;s uniform interface.<\/p>\n\n<p>The good news is that not all of the Web services specs have this problem.\nSome off the top of my head that I consider more or less workable on\nthe Web (not to suggest that they&#8217;re otherwise without fault, and also\nnot to suggest I&#8217;ve had a serious look at every spec out there, even\nthese) include SOAP, WS-Security, and SAML.  If that&#8217;s what Jon has in mind,\nthen we&#8217;re good to go.  But if he was thinking about the likes of UDDI, the\nvarious reliability specs, transactions, etc.., I&#8217;d have to disagree with\nhim.  We need capabilities provided by solutions which were built with\nthe Web and REST in mind, like those of the Semantic Web and\n<a href=\"http:\/\/www.ics.uci.edu\/~rohit\/ARRESTED-ICSE.pdf\">ARRESTED<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"Jon Udell urges the REST movement to not dismiss SOA. Specifically &#8230; Now that the benefits of REST are abundantly clear, it&#8217;s time to circle back and ask when REST isn&#8217;t sufficient. The answer is that we&#8217;ll need the kinds of capabilities WS-* provides as our point-to-point, client\/server-like applications evolve into webs of communicating services. [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[22,26],"class_list":["post-713","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-rest","tag-soap"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/713","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/comments?post=713"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/713\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=713"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}