Tuesday, 4 May 2010

Governance Causes SOA Projects to Fail?

I got spammed with a mail about a Methodology for SOA that contained a very intriguing thought:

.. it is not poor governance that causes SOA failures but rather governance itself is a single point of failure and a pessimistic organizational structure that causes SOA to fail.

It reminded me about a presentation I attended at the LAC 2009 conference, by Frank Schalkwijk (Atos Origin), on Emerging Architectures. He argues that it's better to 'engage' our specialists than to 'govern' them. That way an architecture can 'emerge' with a lot more support in your organization. Hmmm.


  1. Is the problem you describe a matter of terminology? Can the issue be dealt with by using words other than "governance" to describe the process? Ultimately, isn't this a matter of perception and preconception.

  2. Bob, first of all, I'm not so sure it really is an issue. But it can be. Whenever it is an issue, it usually is a cultural issue that you need to address.

  3. Dear Van Alst,

    my comment is related to SOA Suite, when I am using AD(active directory) for security authentication in SOA Suite 11g how I can get the manager of the user or "report-in" users for a AD user.
    do I have to write the function to connect to AD and return the user or it can be done easily.

    Thanks for your attention
    Amir Khanof

  4. @Amir: a bit out of scope, but it does depend on what you aim to achieve. Oracle SOA Suite security can be based upon AD, there's out of the box functionality available. If you want a broader approach to security, have a look at Oracle Access Management.