Migrating to a service-oriented architecture, Part 2
Introduction and overview continued
From the developerWorks archives
Date archived: January 5, 2017 | First published: December 16, 2003
This is the second part of the introduction in a series of articles intended to help you better understand the value of a service-oriented architecture (SOA), and to develop a realistic plan for evaluating your current infrastructure and migrating it to a true service-oriented architecture. It is intended that after reading this paper, you will understand why it is claimed that a SOA is the best platform for carrying existing assets into the future, as well as enabling the rapid and correct development of future applications. Further, you should have a better understanding of the major considerations in planning such a migration. Part 1 of this paper described some of the forces driving consideration of a SOA, and the requirements that might be placed on the architecture. Part 2 continues now with the discussion of services and interfaces.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.