Horizontal and Vertical SOA Governance

| by Jean-Jacques Dubray Follow 3 Followers on Jan 22, 2009. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Rick Sweeney, an Enterprise Architecture consultant, shared his views on getting started with SOA Governance.

He explains that:

The problem is how do you transform a culturally entrenched legacy process of governance based in traditional “stove-pipe” application design to a process that achieves the benefits of SOA?

The answer is “horizontal” and “vertical” governance approach.

As a matter of fact, he defines governance's mission as:

“To never let how we process business dictate how we conduct business.”

In his views, the former is the responsibility of the Service Provider Domain and the latter is responsibility of the Service Consumer Domain. This means that

The vertical (service provider) governance is focused on building services that accurately and efficiently maintain the “logical to physical” relationship between each constructed service and the physical legacy applications and data stores supporting the service.


The horizontal (service consumer) governance is focused on how those services are delivered to the consumer in an efficient and engaging manner that results in a positive experience for the consumer. They are responsible for governing the delivery of services consistent with the corporate mission, strategy and business plans.

Rick also sees the need for a third component: the Enterprise SOA Governance group. Its role is to:

They ensure that the needs of both service providers and service consumers are met. They are also responsible for validating that all enterprise level requirements like Security and Service Level Agreements are met.

Horizontal governance should be responsible for the presentation layer, the delivery channel layer and the business process layer, while Vertical Governance should focus on the business service layer, the integration layer and the legacy infrastructure layer.

For Rick,

The most critical value of this split between horizontal and vertical governance is that it creates a barrier to force the governance participants away from traditional “stove pipe” thinking.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you