Hi Keith, Sorry for the delay in responding. I wanted a chance to do a little research.
Most of what I know about Credit Suisse is summary information from talking with some of our consultants who worked on the project. The Credit Suisse example is also pretty well documented in in "Enterprise SOA" and in somewhat less detail in "Understanding SOA with Web services." For direct information from CS also see: Koch T., Murer S.: "Service Architecture Integrates Mainframes in a CORBA Environment". Proceedings of the Third International Enterprise Distributed Object Computing Conference (EDOC'99), Mannhelm, Germany, 1999. http://uk.builder.com/whitepapers/0,39026692,60022401p-39000951q,00.htm -------------- * Is each service simple to understand individually, or do you have to be au fait with a particular set of complex types developed by Credit Suisse? In ERP, you need quite a bit of initial experience with a package to get up to speed, but can then pick up more aspects of it quickly since you know the basic concepts, types, formats, etc. >> As far as I know the Credit Suisse SOA is based on two distinct "bus" architectures: CORBA for synchronous and WebSphere MQ for asynchronous. Actually CS distinguishes between services = synchronous and events = asynchronous, which is probably where Gartner gets a lot of this service vs. EDA stuff. Whereas most of us (I think) would use the service term for both. But they use CORBA IDL as the contract definition language for both, so the answer is they use CORBA standard types, nothing proprietary. * Are the processes in which the services are re-used dramatically different? Variations on a typical Credit Suisse means of business? Or just versions of one another? >> As I understand it they basically separate infrastructure style or technical services from business services. So they might have a common security service or logging service or something like that that all applications can use. But the main center of design seems to be creating shared reusable business services such as customer lookup, currency conversion, or loan interest calculation. I believe these tend to be centrally located and hosted by one of the CS departments, who then charges back to the other departments according to their use of the service, to help pay for the cost of hardware, software, and operations. The idea seems to be to do things once that can be done once (and eliminate duplicate functions/code) and set up a hosting environment for the service that's capable of supporting the requirements of other applications to access and use the service. * Is the re-use they are gaining via SOA fundamentally different from the re-use they might have expected pre-SOA using components or just program modules rather than services? >> I'm not sure I understand the question exactly but I believe one of the major goals in their SOA project (which has been going on about 8 years now I think) was to better reuse shared or common application functionality and create a more effecient IT environment. So I would say their goals for SOA included things they thought they could not achieve otherwise. --- Keith Harrison-Broninski <[EMAIL PROTECTED]> wrote: > Eric Newcomer wrote: > > >The most recent figures I have from the Credit > Suisse > >case study are 1500 services enterprise wide with a > >reuse rate of about 70%. > > > >The reuse rate was lower when they started out - > which > >is probably obvious enough - and 70% has been > constant > >for a few years apparently, so we could based on > this > >extrapolate a view of the potential max being > around > >that. > > > >But of course the investment in reuse pays off over > >time. > > > Are you able to say anything about the /nature/ of > these services, > Eric? In particular: > > * Is each service simple to understand > individually, or do you have > to be au fait with a particular set of complex > types developed by > Credit Suisse? In ERP, you need quite a bit > of initial experience > with a package to get up to speed, but can > then pick up more > aspects of it quickly since you know the basic > concepts, types, > formats, etc. > * Are the processes in which the services are > re-used dramatically > different? Variations on a typical Credit > Suisse means of > business? Or just versions of one another? > * Is the re-use they are gaining via SOA > fundamentally different > from the re-use they might have expected > pre-SOA using components > or just program modules rather than services? > > -- > > All the best > Keith > > http://keith.harrison-broninski.info > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com 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/
