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.

Article: SOA Governance: The Basics

Posted by Stefan Tilkov on Jun 11, 2007

Sections
Enterprise Architecture
Topics
Governance ,
SOA
Tags
SOA Adoption ,
policy ,
Organizational Patterns
In a new InfoQ article, MomentumSI's Ed Vazquez explains the basics of SOA governance, with an explicit focus on the need for a holistic SOA governance model and shared governance principles.

Ed describes the difference between strategic and tactical governance. Quoting from the article,
"Strategic governance" often results in a set of ideal enterprise SOA policy based on cutting-edge technology, evolving standards, and the latest and greatest markitecture (marketing architecture) that the vendors promise will be ready to ship "next quarter". On the other hand, "tactical governance" results in which policy gets configured in which SOA platform for specific integrations. Both must be aligned for Governance to occur.
Another concept introduced by the article is "the six pillars of SOA", which in the author's opinion form the basis for a SOA program:

Ed points out that some critical questions need to be answered to formalize the SOA effort (see the article for details). Associating the concept of strategic vs. tactical governance, the "six pillars", and these questions (and their answers), leads to the following diagram:



The article's conclusion is that while both technical and strategic governance need to be in place for a SOA governance initiative to succeed, achieving basic SOA governance can become  a matter of weeks when a pragmatic approach is taken.

Read the full article.
  • This article is part of a featured topic series on SOA

No comments

Watch Thread Reply

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.