{"id":307,"date":"2004-03-16T12:45:00","date_gmt":"2004-03-16T16:45:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=299"},"modified":"2004-03-16T12:45:00","modified_gmt":"2004-03-16T16:45:00","slug":"jim-and-savas-on-services-and-resources","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2004\/03\/jim-and-savas-on-services-and-resources\/","title":{"rendered":"Jim and Savas on services and resources"},"content":{"rendered":"

Jim writes<\/a>,\nregarding a diagram by Savas<\/a>;<\/p>\n\n

\nIt shows that managing virtualised resources across organisations isn’t scalable, whereas composition of services is. Why the difference in terms of scalability? In the service-oriented view, services can manage whatever backend resources they have for themselves, therefore the complexity of the application driving the services increases linearly with the number of services. In the resource-oriented view, the consuming application must deal with each resource directly and so complexity increases as the sum of a multiple (the number of resources) of each service.\n<\/blockquote>\n\n

Aside; I think Jim’s using the WS-RF<\/a>\nnotion of “resource”, which is cool, since it jives so closely with the Web’s notion of one\n(stateful resource, stateless interaction).<\/p>\n\n

I think the scalability claim above is only correct if you ignore a whole class of useful\nresources; containers which contain other resources. So I could layout a resource\ncentric view of the network in that diagram to look exactly like the service centric\nview Savas draws. For example, I might define a container called “the aggregate log ‘file’ of\nall devices in this building”, and this might be dynamically constructed in basically the\nsame way that aggregate RSS feeds are constructed. And, of course, it would be given a\nhttp URI so that I could snarf data from it. Each log entry could also provide the URI of\nthe more granular “device” that it came from so that I, or an automata, could visit there\nto find its current status.<\/p>","protected":false},"excerpt":{"rendered":"Jim writes, regarding a diagram by Savas; It shows that managing virtualised resources across organisations isn’t scalable, whereas composition of services is. Why the difference in terms of scalability? In the service-oriented view, services can manage whatever backend resources they have for themselves, therefore the complexity of the application driving the services increases linearly with […]","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-307","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/307","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=307"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/307\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=307"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=307"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=307"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}