Last night I was thinking how close SOA is getting to REST, and how\ngosh-darn frustrating it is to me that its proponents don’t yet see it.<\/p>\n\n
Let’s summarize the state of affairs circa late 2004 …<\/p>\n\n
Document style services<\/strong>. Web services have attempted\nto escape the RPC style of service, and instead advocate a “document in,\ndocument out” model due to its superior loose coupling. Hurrah! That’s\na REST style interaction! In particular, a POST operation; representation\nin, represent out, with simple “process this” semantics. Unfortunately\nmany people don’t appreciate that it’s a uniform semantic (though\nsome do<\/a>)\nand still insist on associating service specific semantics with such an\ninteraction. But the good news is that just makes for tightly coupled\nclients, not services.<\/p>\n\n Identification<\/strong>. For such a so-called cornerstone\nspecification, it took an awfully long time to arrive, but WS-Addressing\nis an attempt to have a standard for Web services identifiers.\nStandardized identifiers? Who knew?! 8-) Of course, REST also requires\na single identifying standard which can be used to identify an endpoint\nfrom which either a representations can be retrieved(GET), or one can be\nsubmitted for processing (POST) (or anything else which can be done to\nall other identified things). See the similarities?<\/p>\n\n When compared with the implicit architectural style of Web services\ncirca 2000 then, we see a movement towards adopting the additional REST\nconstraints of\nresource identification and the uniform interface<\/a>\n(albeit, IMO, an overly constrained uniform interface; basically POST semantics only),\neven if they’re not done in a Web architecture friendly manner.<\/p>\n\n This is *NOT* a coincidence!<\/strong> Once you set out with\ndocument orientation, REST is where you will, for most people, eventually\nend up (though it’s by no means\nthe<\/a>\nend<\/a>\nof the journey).<\/p>\n\n I’ve said it before, and I’ll say it again now; the Web is what\nWeb services are trying to be<\/strong>. There’s just (at least) one enormous\nsacred cow<\/a>\nyet to be\nslaughtered<\/a>,\nIMO, before this can be fully appreciated.<\/p>","protected":false},"excerpt":{"rendered":"Last night I was thinking how close SOA is getting to REST, and how gosh-darn frustrating it is to me that its proponents don’t yet see it. Let’s summarize the state of affairs circa late 2004 … Document style services. Web services have attempted to escape the RPC style of service, and instead advocate a […]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-590","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/590","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=590"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/590\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=590"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=590"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=590"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}