If not all questions are addressed to Steve, I would say that batching may be both - service and service feature, though I prefer the latter. For "Billing Service", it might be an FTP-based interface, for example.
I had such thing once - I built a PKI-based system where new PPKeys might be obtained by participants on-demand (Web Service interface) as well as via FTP channel (interface) where the service posted the keys on a schedule. - Michael ________________________________ From: Rob Eamon <[email protected]> To: [email protected] Sent: Thursday, January 29, 2009 11:36:25 PM Subject: [service-orientated-architecture] Re: [ZapFlash] Batch Processing with SOA What are people's thoughts about batch processing being an "application frontend" and thus not a service but a service consumer? Steve, at what level do you position batch processing? Where on a BA diagram would "batch process" be depicted? Is "batch processing" a service in and of itself or is it an attribute/character istic of a 'proper' business service? For example, assuming "Billing Service" is one of the identified top-level services, would batching be just another operation/interface next to the "one-off bill" operation? -Rob --- In service-orientated- architecture@ yahoogroups. com, Steve Jones <jones.steveg@ ...> wrote: > > Couldn't agree more that batch processing can be better handled as a > service, its one of the "odd" things that vendors seemed to exclude > because it wasn't in their product set (or worse claim an old ETL as > SOA just to get some more license sales). > > Steve
