Yours is the best description I've seen so far, Michael. IMO, it has much to do with understanding for the procurement side of systems evolution where one sees descriptions of services to be procured versus data to be provided as part of that service. The data may include a finite or open ended set of kinds and types where the service is a single line item from the point of view of the procurement. That is why, I believe, when reading RFPs and RFIs I see SOA far more often than ROA.
len
But maybe it wouldn't be too much to hope that we could all just get along by understanding that when a system is best conceptualized as a set of services, service-oriented technologies make a lot of sense ... and when a system is best conceptualized as a hyperlinked web of resources, REST technologies make a lot of sense. Of course, whether a proposed application is best conceptualized as a ROA or SOA is going to be an interesting discussion for the designers to have.
|