InfoQ

News

Can a Spoonful of Governance help SOA?

Posted by Jean-Jacques Dubray on Oct 29, 2008 01:00 AM

Community
SOA
Topics
Governance
Tags
Best Practices

In an article last week, Steve Stefanovich, a principle architect at RDA Corp. asked the question "do you have a governance plan?"

Visions of endless meetings and committee reviews immediately give you that queasy feeling in the pit of your stomach.

But he continues

Don’t let the term, "governance" strike fear in your heart while planning your Service Oriented Architecture. You might already practice governance and don’t even know it...it is simply a reorientation and formalization of many of the things good software architects have been doing all along.

He sees Governance as allowing you to:

proceed in a proper, consistent, and repeatable manner. Consistency is essential when designing, building, deploying, and managing services across an organization.

This view is somewhat similar to Todd's view:

My view on governance is that it is about guiding an organization to a desired behavior.

Steve divides SOA Governance into:

design-time governance [which] covers the analysis, design, construction, and deployment phases [and] run-time governance [which] applies to operations and maintenance.

Others, such as Gary So, a VP at Software AG, sees a bit more granularity:

  • Architecture governance
  • Service governance
  • Design-time governance
  • Run-time governance
  • Change-time governance

Neil Macehiter recently also added Data Governance to the realm of SOA Governance.

Steve provides then a series of recommendations for each phase of service construction based on the following principle:

All the experience and all the proven practices you learned pre-SOA still apply in the SOA world. Understanding that helps you understand that governance is your friend and no SOA is complete until a governance plan is part of the design.

Before concluding:

A spoonful of governance helps SOA go down in a most delightful way.

Where are you in your SOA Governance effort? Have you covered the entire lifecycle? Is it integrated within a more general IT governance process? Are you using SOA Governance suite? What kind of issues are you confronted with at run-time?

  • This article is part of a featured topic series on Governance

No comments

Reply

Educational Content

JRuby: The Pain of Bringing an Off-Platform Dynamic Language to the JVM

Charles Nutter discusses bringing JRuby to the JVM, why Ruby is hard to implement, JIT compilation, precompilation, core Ruby implementation, Java library access, library challenges and future plans.

Performance Anti-Patterns in Database-Driven Applications

Alois Reitbauer specifies several architectural anti-patterns that one should stay away from and which can downgrade an application’s performance.

Making TDD Stick: Problems and Solutions for Adopters

Teams in large organizations still struggle to adopt TDD. In this article Mark Levison shares problems he uncovered when he surveyed teams, and his own strategy to introduce TDD into an organization.

Testing is Overrated

In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?

VM Optimizations for Language Designers

John Pampuch discusses the HotSpot compiler, the history of Java performance, HotSpot development philosophies and challenges, optimization, JVM library improvements, and tips for better performance.

Keith Braithwaite, an Agile Skeptic

In this interview, Keith Braithwaite, an Agile developer, consultant and trainer, says that we should show a good deal of skepticism towards today’s Agile practice.

Workflow Orchestration Using Spring AOP and AspectJ

This article demonstrates how to build and orchestrate highly configurable and extensible yet light-weight embedded process flow using AOP techniques with Spring AOP and Aspect J.

Embrace Uncertainty

Jeff Patton explains why one needs to embrace uncertainty in order to succeed with his/her Agile project and how to avoid some of the common mistakes leading to project failure.