In other words, an ETL-style interface is just another interface of a service?
-Rob --- In [email protected], "Steve Jones" <[EMAIL PROTECTED]> wrote: > > In a project, which was the first one I architected as SO, we had a > whole bunch of services, some using RMI, some Local->Local and two of > them were large message based bulk load... ETL. > > The Customer Service had a "child" service, CustomerUpdate and the > ProductManagement Service had a child service of ProductUpdate. The > two Update services were bulk uploaders (hence the reason for > detaching them from the main service, although no services in the rest > of the application could get to the Update Services which were only > accessible from the Mainframe data dumps. > > The reason for this was to have a clear structure over what the domain > was of the ETL, the Product guys built their uploader and the Customer > guys build the Customer one. This made sure that the ETL fitted in > with the data and behaviours of the overall customer and product > services. > > So yes you can do ETL in an SOA way... but ask them what the > _Services_ are and what the context of those services is, ETL _must_ > be subservient to a wider business service or its just traditional > data dumping in a new guise. > > Steve
