{"id":80,"date":"2003-01-18T13:56:00","date_gmt":"2003-01-18T17:56:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=233"},"modified":"2003-01-18T13:56:00","modified_gmt":"2003-01-18T17:56:00","slug":"composing-web-services-choreography-vs-routing","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2003\/01\/composing-web-services-choreography-vs-routing\/","title":{"rendered":"Composing Web Services; Choreography vs. Routing"},"content":{"rendered":"

Simon Fell says<\/a> that\nhe has trouble understanding some of my arguments, in particular\nthis one<\/a>\nwhere I attempt to outline the value of pipe-and-filter style composition over a\nchoreographed solution. Let me elaborate here then.<\/p>\n\n

It’s long been recognized that composition of components is simpler and more\ntractable when those components share an interface, if only because you can reuse\nglue code. For example,\nthe code written to late-bind the Unix commands “ls” and “more” into “ls | more”,\nis split between the stdout-using code of “ls”, the stdin-using\ncode of “more”, and the binding code in the shell that processes “|”.\nAll of that code is reusable in more contexts than piping “ls” into “more”.<\/p>\n\n

My examples were meant to show the strong similarities between Unix style composition,\nand REST style composition. REST, by itself, supports two styles that I’m familiar\nwith, which I described there; composition-by-URI, and intermediary routing. The\nlatter is more powerful and flexible, but the former easier to use, though at the\ncost of not being standardized (not that it should …).<\/p>\n\n

From what I can tell, the Web services answer for composition lies with\nchoreography<\/a> (and\nsome<\/a>\nin that thread appear to\nagree<\/a>\nwith that). I believe this approach will ultimately fail, and that routing (ala\nWS-Routing<\/a>,\nPEP<\/a>,\nIdokorro<\/a>,\nKnowNow<\/a>) will prevail.<\/p>","protected":false},"excerpt":{"rendered":"Simon Fell says that he has trouble understanding some of my arguments, in particular this one where I attempt to outline the value of pipe-and-filter style composition over a choreographed solution. Let me elaborate here then. It’s long been recognized that composition of components is simpler and more tractable when those components share an interface, […]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[26,40],"class_list":["post-80","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-soap","tag-xml"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/80","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=80"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/80\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=80"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=80"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=80"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}