David Linthicum, in his recent blog post defines two categories of SOA governance:
SOA Governance Technology There are two types: running, or service strategy is to strengthen the implementation capacity.And design, or support the service strategy design and implementation of technology.Placed in service around the strategy for the control who can access services, and can do something.
To Dave's point of view, cloud computing is fast becoming the most popular trends in many enterprises, it will effectively erase the design of the SOA governance, and tend to run-time governance:
... ... Concerned about the run-time execution of services can bring more value.Many existing players SOA governance provides sufficient capacity to design and implement, so the design of a separate tool is no longer needed.Cloud computing simply accelerated the run-time SOA governance concerns, and design treatment will sooner or later the stage of history.
K. Scott Morrison and Dave the same point of view, he said:
The Epoch Times in the SOA (January 1, 2009 before), the design of governance is king.It is very consistent with large enterprise SOA program - management - the principles of control ... ... in contrast, run-time governance is often seen as the work can tow a trailer ... ... the cloud changed the order of priority between the two.Even if you deploy only cloud in the public a service, you must be ready to run-time governance.
In his view, the design of governance will not completely disappear, but it will be the only growth in the SOA's value (compare my original notes):
Finally, the cloud of governance priorities in the final analysis is a very simple principle: the definition of a function may not lead to duplication of losing your job; and if you leave the back door of the destruction of corporate data is possible.
William Vambenepe further explore this topic, he defined a SOA + + model (the service center IT management), unified framework, API, models and tools:
All IT resources ... ... can be thought of as services that can be consumed (eg, exposed by the hypervisor "X86 + Ethernet Simulation" services exposed by the application server "J2EE-compliant platform" services exposed by the database "RDB Services"HTTP-SOAP-based or XML / JSON exposed Web services.)
Just a simple API to the service provider sends a request, they can be the same as the service was established.
They not only want to serve the same is established, but also the same as the service structure of the document through the good (usually standard) interface call.
They also serve as the center similar to the approach to management, such as through the performance scale, SLA, strategies.
You may want to have to deal with three types of scheduling code (for example, when applied to slow down, it may adopt the following three ways: modify the application dependent, re-configure the infrastructure, or launching a new deployment).
The relationship between these three categories may be introduced across organizational boundaries and external providers, the service may be charged.
In this way, your IT automation systems do need a simple, consistent, standard way to handle these relationships.After you have been simplified and standardized (automated will be applied to the) environment, the automation to achieve the best results.
In this model, service or container by supporting well-defined strategies and SLA with the quality requirements defined in the operating contract.As a result, they require a management framework to monitor these strategies and the SLA, a measure of public safety, infrastructure or billing, etc. - this is a completely full of run-time governance.
SOA and cloud computing lit close cooperation between the SOA runtime governance of the importance of this is good, but it is neglected for the design of governance seems to be ill conceived.End, SOA is still the business and commitment to IT alignment, and if the design services business model no longer refer to the decomposition of business practice it is impossible promises.This means that the design of a true SOA governance remains the core of the implementation.The focus of debate should not be what SOA governance is more important, but how to properly implement them.