We need an organizational mechanism to transfer knowledge, implement standards, create an infrastructure for development and changes, and in general Presentation Strategic leadership We have for our service oriented architecture.
To achieve this goal, a Center of Excellence, SOA Governance board or Competency Center consisting of investors Create technology and business.
Depending on the size and maturity stage of the organization, IT standards may be available, and in fact SOA governance is extended It is the governance of IT that is assigned for the purposes of SOA. And since SOA expresses an initial state of strategy, We need to define a strategy for our organization.
SOA requires new processes, so in your organization, how to design service candidate selection, SOA based solutions and coordination of the production cycle should be determined.
Establishing governance in the service placement of system architecture, solutions and also business capitalists in COE gives us this assurance It ensures that IT is aligned with the business and has access to future plans and current priorities. Responsibilities which the body of this government is responsible for, is as follows:

Create business case
This responsibility by architects or other members of the SOA is done at the very beginning. The business model in SOA includes: insights, goals that SOA realizes them as well as financial planning for expenses.
General rules
Definitely, SOA introduces new rules of IT and these rules must be clearly explained. here to People responsible for doing governance work, architectural decisions, creating reference architectures, vet services, service candidates We will need the process and creation and development of new infrastructures (such as ESB). You can also decide who is responsible maintain and support the service after its release and ensure; The knowledge transfer plan is considered for this Is.
help to determine the work plan
The governance team has a specific scope that helps the enterprise architect or technical executive define the IT roadmap. Map The path goes so far as to map defined activities to larger goals, and those goals to aggregates Greater aspects of business insight are drawn.
Maintain the reference architecture
The COE can also take on the maintenance of the reference architecture within its domain, which involves building and connecting process models Big companies help.

Facilitating design-time development
Architects guide programmers in this field, thus enabling reference architectures and such efforts Programmers support. They can choose tools, frameworks and software to support service-oriented organizations infrastructure and methodologies.
Improve services at runtime
Governance also includes programmers and services. Runtime monitoring tools should ensure visibility SLAs are available. And this is in the domain of governance to trace and plan future developments; so that before The emergence of new requirements inform us about them.
Service Lifecycle Improvement
The governance team determines when services should be versioned and contributes to the effects of this versioning. Versioning in SOA seems to be more complex than its traditional form and this is due to its distributed nature. The team or individual responsible for creating a service may have no idea about the larger set of processes and it is the duty of the governance team to have this understanding and preparation and monitor its correct implementation.
Sovereignty, help to avoid common pitfalls
SOA without governance can be considered a failed SOA due to very common pitfalls. Can not rule anything Payment that we are not aware of. Therefore, a central repository is needed to ensure that all code and documentation are tangible Have a copy of each service for document storage. It follows documentation during design and runtime makes it easy
Service Redundancy
A common pitfall (especially in large and decentralized companies) is the redundancy or overlapping of services in such a way that the same service in Different groups are made several times. Such a function is costly, useless and confusing, as well as maintenance cost It will be high. It is the COE's job to monitor what is being built to prevent such practices, and communication Build between execution and production systems and use a central repository for service discovery.
Destroying by using abbreviations
If we expect everyone to fully understand acronyms, we are wrong. Because complex concepts They are expressed as abbreviations, if only its general and apparent meaning is tangible. And this is how teamwork is impaired will be
The only way to get rid of this problem is education and training, so that in SOA, to understand the concepts, you only have to look at one source. Let's not settle.
Resume padding
To architects and programmers who only think about the progress of their work, even at the cost of adding unnecessary tasks and solutions. Note over-engeering.
Governance can solve this problem by clarifying service development efforts and managing solution implementation.
rabbit services
Keeping a rabbit at home is fun, if you increase the number of rabbits to two, it can be even more fun, but if Make that number fifteen, and they will definitely be a problem. The same is true for services, they should not be out of balance It went out and turned everything into a service.
Remember that not everything that can be a service needs to become a service.