SOA What?

A recent article providing SOA implementation tips argues in part, that SOA is a transformational technology with great value – but transformation comes with prerequisites for careful planning and implementation as opposed to something that is just dropped into an IT shop. For example, the operations and management of both the architecture and newly developed services need to be considered by IT operations.

More often than not, I find most IT operations groups are aware that a SOA is being designed, services (versus applications) are being developed, and business processes are being modeled and mapped to these services. However, IT operations groups often have ITIL process improvements and BSM initiatives underway and want to know how this new technology architecture will affect current operations, processes, and how they should plan for the future.

As such, I’m often asked, “Does your technology support SOA?” Quite simply, the answer is yes, Managed Objects can manage the new SOA infrastructure; provide bi-directional integration to a SOA-based infrastructure; and manage SOA services via integration mapping processes and transactions/activity to supporting technology.

However, the more important question that should be explored deals with dependency. What impact will this new architecture have on projects such as configuration management – as in the CMDB (also referred to as the configuration management system or CMS)? If IT operations thinks current CMDB projects are challenging – consider for a moment “decomposing” those legacy applications into many smaller pieces like Lego blocks: the complexity of the CMDB just exploded in scale and in the sheer volume of CI’s and relationships.

The future challenge and success will rest upon building sound change, configuration and CMDB foundation today. A well constructed CMDB will reap many rewards going forward regardless of new technologies and architectures.

SOA is dependent upon a CMDB that is constructed with the least amount of constraints and is flexible enough to receive inputs from different technology in the future to deliver to the requirements of the future as they evolve. Maximum control with the least amount of data is the best rule of thumb and do not be constrained by today’s technology and requirements.

- Michele