{"id":1266,"date":"2006-02-06T21:58:00","date_gmt":"2006-02-07T01:58:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/2006\/02\/06\/wsdl-interoperability-and-silos\/"},"modified":"2006-02-06T21:58:00","modified_gmt":"2006-02-07T01:58:00","slug":"wsdl-interoperability-and-silos","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2006\/02\/wsdl-interoperability-and-silos\/","title":{"rendered":"WSDL, interoperability, and silos"},"content":{"rendered":"<p>From\n<a href=\"http:\/\/www-128.ibm.com\/developerworks\/blogs\/dw_blog_comments.jspa?blog=392&amp;entry=107058&amp;ca=drs-bl\">Bobby Woolf&#8217;s latest<\/a>;<\/p>\n\n<blockquote>\nThe beauty of interoperability is that two systems developed completely independently can still work together. Magic? No, standards (or at least specifications, open or otherwise); see Open Standards in Everyday Life. Consider a Web services consumer that wants to invoke a particular WSDL, and a provider that implements the same WSDL; they&#8217;ll work together, even if they were implemented independently. Why? Because they agree on the same WSDL (which may have come from a third party) and a protocol (such as SOAP over HTTP) discovered in the binding.\n<\/blockquote>\n\n<p>So what about the services that expose WSDL that the client doesn&#8217;t know about?\nWhat&#8217;s the possibility of those components <em>ever<\/em> interoperating without\nsoftware upgrades?  Zero, of course.  That situation is called a <em>silo<\/em>, and\nI thought one of the main objectives of this whole SOA thing was to avoid them &#8230;\nwasn&#8217;t it?<\/p>\n\n<p>Sigh &#8230; how many ways do I have to keep\n<a href=\"http:\/\/www.markbaker.ca\/2002\/09\/Blog\/2006\/02\/05#2006-02-lego\">saying<\/a>\nthe\n<a href=\"http:\/\/www.coactus.com\/blog\/2005\/11\/on-interface-and-implementation-and-reuse\/\">same thing<\/a>?!?!<\/p>","protected":false},"excerpt":{"rendered":"From Bobby Woolf&#8217;s latest; The beauty of interoperability is that two systems developed completely independently can still work together. Magic? No, standards (or at least specifications, open or otherwise); see Open Standards in Everyday Life. Consider a Web services consumer that wants to invoke a particular WSDL, and a provider that implements the same WSDL; [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[26],"class_list":["post-1266","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-soap"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/1266","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=1266"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/1266\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=1266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=1266"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=1266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}