| Title: |
SOA - Save Our Assets |
| Author: |
Lawrence Wilkes |
| Publication Date: |
12 November 2003 |
| Report Type: |
Journal |
| Report Class: |
Best Practice |
| Abstract: |
Strategies for Reusing Existing and Legacy Applications as Services
Service Oriented Architecture might be the normal interpretation of SOA, but for many organizations Save Our Assets seems more appropriate. When any IT paradigm shift occurs, the first reaction will normally be "can I reuse my existing assets?", and in this report we examine the opportunities and approaches, and assess the suitability of existing systems to participate in new Web Service scenarios.
|
| Backgrounder: |
As the scope of Web Services has expanded beyond the original narrow vision of external object access, then the range of assets that organizations expect to reuse and the scenarios in which they want to apply them has grown significantly. Is it reasonable to expect that complex enterprise systems, often monolithic in nature and some of which have been around for decades, can be exposed as Web Services with little more than the point and click tooling that those first Web Services used? Or is it going to require significant re-engineering of those systems before they can truly take part in the dynamic, federated, on-demand future? The answer can be yes to both questions, though more likely the solution is going to be somewhere in between. |
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|