Solution isolation in service-oriented environments
From the developerWorks archives
Date archived: January 3, 2017 | First published: March 30, 2011
Many IT environments are often designed and deployed in what you might call a vertical fashion. This means that each line of business has its own set of solutions, which are isolated from each other. Among other things, the concept of SOA is an attempt to establish a more horizontal view, promoting better reuse of IT functionality and operational resources across organizational boundaries. And while this is all good, of course, it requires extra care and due diligence to achieve operational excellence. This article describes some of the operational challenges introduced by this view and suggests approaches for how to address them, namely by isolating solution components from each other. Included are examples showing how this isolation can happen on many levels, either individually or in concert, all based on a set of prioritized criteria. This content is part of the IBM WebSphere Developer Technical Journal.
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.