[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [soa-rm-ra] OO vs. SOA and what goes into a service
Without meaning to turn this into a REST vs. SOAP debate (to mix the two, I could send a SOAP 1.2 envelope with an HTTP methods called through the web methods option), consider the following: I develop a service that does a read of a resource and I can give it the resource identifier. I develop another service that does a save of a resource and I give it what I want saved and the identifier of where to save it. I develop a service that can delete a resource and ... you get the idea. Or I can say I want to read, save, delete, ... a timecard record and I develop a timecard service that includes independent operations for read, save, delete, ... Now I know what the service description looks like for the REST-like example, but I can see increasing complexity if the timecard operations each have a different payload and each have different policies and each ... I've got a new write-up of service description that tries to capture and better present the essence of this that was in the v0.2 text. However, having gone back through old email threads, I wanted consensus on what the problem and solution space looks like. A dominant idea for me is if you can't easily describe it, you will have trouble with visibility, and you probably have something that shouldn't be a single service. More emails in this thread to process. Ken On Jan 22, 2008, at 6:58 PM, Danny Thornton wrote:
----------------------------------------------------------------------------- Ken Laskey MITRE Corporation, M/S H305 phone: 703-983-7934 7151 Colshire Drive fax: 703-983-1379 McLean VA 22102-7508 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]