Keith, I can share my experience on services reuse in a Telco environment. We had something 600 different services in production. Each service had one and only one operation. The overall reuse ratio was 2.1. It means one service was used by more than 2 applications average. Not all services were reused equally. The "best selling services" were reused a lot, some of them by more than 30 applications. Those services were on top of reference data like customer, contract or product data.
Some services were not reusable at all because too specific for a particular process. It took 7 years to have such a service portfolio. The core technology was not Soap, nor XML but support of web services is actually an on-going development. The key element to achieve reuse was the central repository where the meta-data about each service was available and it was possible to search for available services according to certain criterias. --- In [email protected], Keith Harrison-Broninski <[EMAIL PROTECTED]> wrote: > 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/
