![](\"\/images\/snowball.jpg\")
\n\nAs if on queue, the Zapthink guys release a\nreport<\/a>\nwhich shows that they’ve been paying attention;<\/p>\n\n and …<\/p>\n\n I really like that second last sentence, where they’re saying, no, SOA does not<\/em>\nencompass all forms of service<\/a>.\nAnd though they don’t explicitly state what they do<\/em> think SOA entails,\nit’s made clear that their interpretation of SOA does not include “the simple\naddition of Web Services interfaces”, which seems to mean that they include\nsome sort of interface constraint.<\/p>\n\n Some of those snippets are taken somewhat out of context; as you’d expect,\nthere’s a bit of the “SOAP is for heavy lifting” stuff in there too. But still,\nfrom these historically foaming-at-the-mouth WS\/SOA types (kidding guys! 8-),\nsome good stuff.<\/p>\n\n Tags:\nsoa<\/a>,\nrest<\/a>,\nweb<\/a>,\nwebservices<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"As if on queue, the Zapthink guys release a report which shows that they’ve been paying attention; Since the Web plays such a large role for SMBs in their use of Web Services, it makes sense that many of them use the cheapest, simplest approach available for implementing B2B Web Services interactions. Using approaches such […]","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-1299","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\/1299","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=1299"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/1299\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=1299"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=1299"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=1299"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\nSince the Web plays such a large role for SMBs in their use of Web Services, it makes sense that many of them use the cheapest, simplest approach available for implementing B2B Web Services interactions. Using approaches such as Representational State Transfer (REST) gives companies a simple, straightforward HTTP-based approach to Web Services-based integration that is adequate for the needs of many SMBs.\n<\/blockquote>\n\n
\nMany SMBs have been leveraging Web Services to reduce the cost of older approaches to addressing their external integration needs. The simple addition of Web Services interfaces, however, typically remain as inflexible as the API approaches that came before. Only through the application of SOA can midsize firms build and leverage loosely coupled Web Services that are flexible enough to respond to ongoing change in the business environment.\n<\/blockquote>\n\n