\n
During the speech Rich draws a simple picture, which I believe deserves some meditation. Below an approximate reproduction.<\/P>![](\"http:\/\/www.maseghepensu.it\/oldblogrecovery\/Boundary.jpg\")
\n
The red line represents a service boundary, and all the black things… all the things which live inside those boundaries. Objects, components, data, etc etc. Have you watched the last MSDN TV episode with Richard Turner? It’s a short but instructive view, I suggest you to check it out. During the speech Rich draws a simple picture, which I believe deserves some meditation. Below an approximate reproduction. The red line represents a service boundary, and all the black things… all the…<\/p>\n","protected":false},"author":1,"featured_media":1508,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[61],"tags":[],"class_list":["post-739","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-architecture-ws"],"_links":{"self":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/posts\/739","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/comments?post=739"}],"version-history":[{"count":0,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/posts\/739\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/media\/1508"}],"wp:attachment":[{"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/media?parent=739"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/categories?post=739"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cloudidentity.com\/blog\/wp-json\/wp\/v2\/tags?post=739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
That is nothing strange, we have all digested the autonomy tenet so we should expect <\/EM>to have things which are at exclusive disposal of the service (hence inside its boundaries). This view, perfectly accurate, nas to be reconciled by all those diagrams where a service is depicted as a simple box or it is identified just by the corresponding web service. Would not be correct to say that the web service just sits <\/EM>on the service boundary, rather than being<\/EM> the boundary? Topologicly-wise, the two things may seem the same (after all, the only way to reach those resources IS (or should be) the webservice) but concept-wise I prefer to stick with the sit option: it helps avoiding to fall in the trap (component:COM+package=service:WebService), which could lead to all sorts of antipattern.<\/P><\/p>\n