InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Is Technology Important for SOA Governance?

Posted by Jean-Jacques Dubray on Jul 29, 2008

Sections
Enterprise Architecture
Topics
Governance ,
SOA
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 SOA
Social Governance by Paul Fremantle Posted
  1. Back to top

    Social Governance

    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

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.