On Jul 13, 2006, at 9:54 AM, Mike Glendinning wrote: > Consider an invoicing system, let's say SAP R/3. A service for a > company's suppliers called "SubmitInvoice" will typically store the > invoice details in the database and kick off a series of internal > processes/workflow to process the invoice and pay the supplier. To > be useful, an information retrieval service > called "GetInvoiceDetails" must also be able to access the data > previously created by "SubmitInvoice". That is, both services are > dependent on the shared SAP R/3 database.
That's why, IMO, these would be two operations of the same service. They are much too closely related to be two services. I believe the concept of autonomous, independently evolvable services usually requires having more than one op per service, with a single- op-service being a special case. Stefan -- Stefan Tilkov, http://www.innoq.com/blog/st/ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
