http://www.lustratusrepama.com/litebytes/best-practices/why-do-so-many-soa-adopters-moan-about-low-reuse-levels/ The Lustratus Research blog - thought leadership in SOA, Cloud Computing and Infrastructure Software Mon, 28 Dec 2009 04:05:29 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://www.lustratusrepama.com/litebytes/best-practices/why-do-so-many-soa-adopters-moan-about-low-reuse-levels/comment-page-1/#comment-6 John Power Mon, 11 May 2009 13:16:12 +0000 http://lustratusrepama.com/litebytes/?p=23#comment-6 Steve, While I agree with almost all of what you have said here, I believe SOA without using standards to implement the services is equivalent to what many organizations have been doing for many years. They build services which are reused in the environment where they are available (e.g. within CICS), however, the problem is reuse outside of these environments. From my perspective, it is only poissible to get this reuse by making these services available using SOAP or REST. To my mind, SOAP is better due to the ability to 'catalog' what services are available in a UDDI repository and thus people can discover _and_ use the esources for themselves without having to review a design doc that is more than likely out of date. Many times services are not reused as people don't want to make an effort to work out how to call them. Delivering services using a WSDL means there is no effort to work out how to use the interface which will encourage further reuse. Some further thoughts on this based on a paper your organization wrote at the following location http://soagateway.blogspot.com/2009/05/best-of-breed-mainframe-integration-and.html. More thoughts on standards here http://soagateway.blogspot.com/2009/04/standards-based-soa.html if you're interested. Best regards, John Steve,
While I agree with almost all of what you have said here, I believe SOA without using standards to implement the services is equivalent to what many organizations have been doing for many years. They build services which are reused in the environment where they are available (e.g. within CICS), however, the problem is reuse outside of these environments. From my perspective, it is only poissible to get this reuse by making these services available using SOAP or REST. To my mind, SOAP is better due to the ability to ‘catalog’ what services are available in a UDDI repository and thus people can discover _and_ use the esources for themselves without having to review a design doc that is more than likely out of date. Many times services are not reused as people don’t want to make an effort to work out how to call them. Delivering services using a WSDL means there is no effort to work out how to use the interface which will encourage further reuse. Some further thoughts on this based on a paper your organization wrote at the following location http://soagateway.blogspot.com/2009/05/best-of-breed-mainframe-integration-and.html. More thoughts on standards here http://soagateway.blogspot.com/2009/04/standards-based-soa.html if you’re interested.
Best regards,
John

]]> http://www.lustratusrepama.com/litebytes/best-practices/why-do-so-many-soa-adopters-moan-about-low-reuse-levels/comment-page-1/#comment-5 Vijay Narayanan Thu, 07 May 2009 01:19:28 +0000 http://lustratusrepama.com/litebytes/?p=23#comment-5 Steve Great points. I completely agree that the build-it they will come approach will not fetch high levels of reuse. I also would like to point out that reuse doesn't magically happen with SOA - there are key design attributes to make services reusable or "sharable". Steve
Great points. I completely agree that the build-it they will come approach will not fetch high levels of reuse. I also would like to point out that reuse doesn’t magically happen with SOA – there are key design attributes to make services reusable or “sharable”.

]]>