InfoQ

News

Is Technology Important for SOA Governance?

Posted by Jean-Jacques Dubray on Jul 29, 2008 10:43 PM

Community
SOA
Topics
Governance
Tags
SOA Appliance ,
Registry

Michael Stamback, who just started a new blog on SOA Governance, asked this question a couple of weeks ago.

According to Michael, a director of Product Marketing at Oracle,

governance is about affecting behavior in order to establish a sense of control over the environment...governance is a process that enforces standards, guidelines, and controls with the purpose of ensuring your SOA stays aligned with the business goals and objectives.  

This definition is well aligned with Todd Biske's definition.

Michael recommends

Everyone involved in the process must be aware of the business goals and objectives. 

Fostering the right culture in support of the governance process greatly increases your chance for success. 

Saba Pathyn noted in his blog last month that:

there is no way to instant “soafication” and it is a strategy that has to be put in place brick by brick where collaborations between various stakeholders and the infrastructure is of paramount importance. Doing SOA right simply boils down to effective governance mechanism in place.

Michael's colleagues argues that technology, such as a Registry and Repository, is equally important:

Providing visibility into assets and their dependencies while automating their progression through the different stages of the lifecycle is critical for obtaining the goal of business agility. 

Without visibility, there is no reuse, and automation of the lifecycle can greatly reduce the need for time intensive, manual compliance reviews, as these can be auto validated in order to progress SOA projects faster. 

They also added:

Governance doesn't stop after version 1 of an application or service is deployed.  Your SOA needs to ensure everything operates within the policies defined by the business requirements, so technology that automates this enforcement at runtime is essential. 

Additionally, your SOA is going to evolve, so you need the ability monitor the behavior of the elements of your SOA to not only ensure everything operates as intended, but also identify areas of improvement. 

Governance is certainly one of the most difficult part of SOA regardless of which technology you use, yet it can greatly impact the degree of success of your SOA initiative. What is your experience? Did the introduction technology helped your SOA Governance effort? or are the cultural and organizational issues simply too overwhelming?

  • This article is part of a featured topic series on Governance
Social Governance by Paul Fremantle Posted Jul 30, 2008 8:37 AM
  1. Back to top

    Social Governance

    Jul 30, 2008 8:37 AM by Paul Fremantle

    I completely agree that cultural issues are vital to SOA governance. We (WSO2) have a technology that addresses the human, social and cultural aspects of SOA governance as well. By using tagging, comments, ratings and integrating with feed readers, the governance tool encourages a whole raft of Web2.0 social governance ideas as well as the more formal technical governance implemented through lifecycles, dependency management and policy enforcement. You can read more here and here.

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.