Good governance, simply put, is a setup of structure and processes that produce results to meet the needs of all stakeholders while making the best use of resources available to an enterprise at any given time.
An API and application integration governance framework should facilitate good governance. It must allow the initiative to evolve, and iteratively present best practices based on results achieved.
The THIS API and Application Integration Governance Framework enables cohesive integration across the enterprise such that all elements are connected, rationalized, and organized to provide consistent guidance and incentives that executives and business unit leaders require.
Formalize roles & responsibilities
Establish standard and best practices
Establish governance process
Define measurement criteria
Figure: Mature governance framework
Building the ability to achieve “automated integration” is key to succeeding with your digital transformation goals. We see senior executive teams committing their time and resources to operationalize governance structures and institutionalize integration principles to be adopted.
Integration governance typically factors in all aspects of governance, from the duties of the decision-making authorities to the integration team structure and operating model, moving into how it translates to B2B and B2C scenarios and people’s day-to-day implementation responsibilities.
through API and
cook-books, rules, decision-trees and principles?
Are we using them the right way?
and Governance tools?
Successful integration governance starts with and hinges on the correct identification of three key profiles:
Application integration maturity assessment framework
To assess whether your policies and guidelines are purely on paper (no matter how clearly and forcefully they are articulated), or whether your people actually have the understanding, motivation and means to implement these and ensuring they do implement them, is determined by the maturity of your governance set up.
The table below gives a snapshot of classification criteria for different levels of maturity
clear vision or budget
and registry tools are
not used; review
processes are not
does not exist
exposed but is highly
subjective to a single
and operations team
does not exist
place and their roles and
practices are defined
architecture is defined
standard and uniform
interface but are not
empowered and has full
support of senior
and re-use are identified
and registry tools are
compliance with best
practices and principles
is defined and published
involves in technical
decision making in
are controlled using
strict and disciplined
and strategy in place
effectively to collect
service usage and
to facilitate automated
parameters are defined
define the service
and strategy to measure
resources are measured
aligned; IT can respond
faster to changing
business needs with
capacity is dynamically
managed with cloud
designed with right
granularity to be
composed in a business
projects of the
organization to be
aligned to integration
state-of-the art tools for
monitoring all technical
resources to ensure
high availability and
quality of service
Integration architecture - principles & decision trees
Building an integration backbone for your enterprise that consistently delivers on business objectives, is no mean task. You will need to consider several factors, including:
- Integration scenarios at both the application and data levels
- Asynchronous and synchronous integration scenarios
- Hybrid integration scenarios
- UI integration scenarios
- Decision trees and Integration rules that determine when to use which integration methodology and technology
Decision trees to determine integration scenarios and appropriate integration target tools
Setting up API governance
Good API governance can be visualized in terms of a chocolate fountain with several levels. At the top level, you have enterprise-wide enterprise architecture governance.
Policies and process enforcement flow from enterprise architecture governance into IT governance. The flow continues from IT and integration governance into API governance.
At the program level, API governance covers the lifecycle stages and demand management. Governance would include overseeing topics such as:
API portfolio management – determining the inputs and drivers, along with the approach:
- Domain driven approach
- Customer journey-based approach
Demand management – types of demand, demand channels and sources
API design guidelines, API identification best-practices, interface design guidelines
Funding & charging models for your API initiative
Best practices for monetizing your APIs
Measuring consumer satisfaction for your APIs
sales & marketing
IT portfolio management
Project portfolio and
API portfolio management
API portfolio and
Typical starting points to determine your API governance strategy would be to identify:
- What are my business KPIs in order of priority and who is the end beneficiary?
- Are there existing user journeys that I could automate?
- What unique data and functionality exist within my enterprise that I can take to new markets?
- What useful insights or trends can I gather from data specific to my business?
- What collaborations can I forge with other industries to create new offers and reach new audiences?
Your governance strategy and structure are very unique to your business. They will encapsulate and deliver upon your drivers and expectations. There is no one-size-fits-all in the case of governance.
Our team of governance consultants can help you with:
API governance team set up – We help plan the team structure, responsibilities and infrastructure required to set up architectural principles and provide guidance on policies to the governed teams. Policy enforcement is a key part of this function.
API governance function implementation – We help bridge the gap between the governance framework and operational realities. Set up sustained governance by creating a feedback loop in which the business can identify and respond to changing needs
API platform governance implementation – We help structure governance related to the API platform, adherence to the separation of concerns, overseeing platform evolution and governance of platform lifecycle.
Governance operating model – We help bring governance to the level of people’s day-to-day job responsibilities, the nuts and bolts with respect to your digital initiative.
Funding models for your API initiatives
APIs are valuable, tradable products, capable of generating huge value for your enterprise.
API product management
API developer support
Therefore, how you socialize your APIs, how you maximize participation and engagement with them and what worth you attach to them have to be carefully envisioned and acted upon.
A few common API charging models used in different customer scenarios are:
- Centralized funding from the IT budget
- Pay per use for APIs built on-demand by Lines of Business (LoBs)
- First consumer funding for API development
- One-time payment for reuse
Impact of the API governance framework at different stages
The THIS Application Integration and API Governance Framework enables governance teams to perform activities that have a steadying effect during each project stage. We work closely with your teams to manage deliverables, monitor success, and create the required feedback loop.
Governance activities by stage:
Requirements → THIS works to analyze your performance requirements.
- Ensure coordination between BA and API service architects to identify service candidates
- Ensure domain experts are consulted to standardize and bring service requirements in line with the business domain
- Approve changes to existing APIs to accommodate new requirements
Solution architecture & design → THIS establishes standards for each stage.
- Ensure solution is in accordance with API standards
- Ensure the right versions of APIs are being used for the solution
- Ensure API design and interface documents are detailed enough for further implementation
Development to production → THIS establishes governance tasks and responsibilities from development - testing - production!
- Ensure services are developed in accordance with defined service contracts
- Ensure that defined service development and security guidelines are adhered to
- Ensure coordination between shared service, development, and project teams
- Ensure execution of service test plans
- Ensure collection of metrics
- Ensure test exit criteria are met in the test exit report
- Ensure consumer’s SLAs are not breached
- Ensure API platform capacity can meet more requests without platform degradation
- Ensure the API service’s security is not breached
Implementing a successful API governance framework
There is no predefined governance structure that intrinsically delivers business benefits. At Torry Harris, we first analyze how clients measure performance, and what their capabilities and constraints are. We then establish a realistic, fit-for-purpose team with clearly defined roles and responsibilities.
These key stages are a part of the topics covered by an application integration and API governance framework for efforts surrounding APIs and integration.
A THIS governance framework covers functional business objectives like:
- Establishing key stakeholders
- Correct ways of API discovery
- Processes for creating consistent API requirements.
- Processes to track re-use and measure RoI
- API lifecycle management
- API charging models
- Processes for managing service capacity
- Establishing SLAs and consumer satisfaction criteria
The role of API/Integration governance is to balance competing objectives to the benefit of all stakeholder interests. The purpose of governance is to align the interests of all stakeholders as closely as possible to the objectives of the organization’s integration-driven digital programmes.