SOA Release management

SOA Infrastructure

• The SOA Reliability Conundrum

• The OSI Stack Revisited

• The SOA Performance Issue

• The XML Processing Problem

• The XML Performance Crisis

• XML traffic on the Network

• XML in the Networked Enterprise

• Transformation: Solving the 80/20 Problem

• Hardware vs. Software Approaches to Improve XML Performance

• Is Moore's Law the Solution?

• Challenges in Content Processing

• Addressing Security Issues

• The Security Context Challenge

• Important Points: Managing Services

• Service-Oriented Management

• Do You need an ESB for Service Mediation?

Architectural flexibility and support for requirements variability across the various departments of an enterprise is one of the key benefits of SOA. Often one department will follow a slightly different process for that particular business sector or domain. SOA provides the mechanisms to enable this type of variability at both design-time and runtime. But this is also a key driver behind product line/application family engineering, a well established software technique. This series of articles explore some of the techniques used for product line engineering that can be used to raise the state of the art of SOA.

We are frequently asked to provide advice on “service versioning”, and explain how to handle upgrades to software services. Service versioning is not a new problem: it has been a consistent challenge with different technical approaches to distributed computing such as CORBA, COM and now Web Services. This report proposes that three main categories of service release should be recognized, and that the release procedures will need to be different for each.

#SOA #Infrastructure #ArchitectureGovernance #EnterpriseArchitecture