Skip to content

API Governance

  • Members: 2
  • Architecture, Security & Compliance

Context

An API is a mechanism that allows one IT system to interact with the capabilities and data provided by another system in order to deliver value on top of these capabilities. APIs are essential to provide the necessary abstractions which make it possible to master the complexity of large, volatile IT landscapes.

API governance is the discipline which ensures that APIs are compliant with desired standards and regulatory requirements, and that they are aligned with strategic goals.

In an increasingly agile environment one of the main challenges is to keep the balance between team-autonomy and an overall compliance. We must ensure flexibility and team responsibility on one hand, and compliance, interoperability and the strategic coherence on the other, without creating impediments by administrative overhead and organisational bottlenecks.

Goals

Review the API Lifecycle and identify typical stakeholders and intentions, sketch influencing factors and aggregate them to typical requirements profiles.

Define a framework or catalogue of possible parameters and characteristics of governance-styles, with pre- and postconditions to address the various needs of the different profiles along the API-lifecycle.

Outline organizational, process and tool prerequisites and requirements for each API governance style and lifecycle stadium.

Required Expertise

Experienced expert who has filled one or more of the following roles or the manager of a respective department or team.

  • IT architect
  • Requirements engineer
  • System owner
  • Product owner
  • Enterprise architect
Add a document to this circle
Document Source *
Maximum file size: 50 MB
Please ensure that visibility permissions for the document are set to Visible to Everyone with a Link. Only Circle Members will have access to the link.
Describe the document in 140 characters.
Connect this document to a meeting?
This document will be connected to this Circle. Check this box if you also want to connect it to a particular meeting.
Edit this circle
Allow members of the EnTranCe Community to apply to this circle as members? Setting this to 'No' will not affect your ability to invite new members.
This will control the URL of the circle
How often does this circle meet? E.g. once a week, once every two weeks, or once a month, etc.
Maximum file size: 5 MB
Maximum file size: 5 MB
Please select 1 to 3 OPFs
Add a New Revision Document
Document Title *
Document Source *
Upload a File *
Maximum file size: 10 MB
Share a Link *
Please ensure that visibility permissions for the document are set to Visible to Everyone with a Link. Only Circle Members will have access to the link.
One-line Description
Describe the document in 140 characters.

Edit Information

Content Type
Replace the Displayed Author with a Circle? *
Selecting 'Yes' will replace the displayed author with a circle of your choosing. Please note that this does not actually change the authors of the Best Practice.
Please select a Circle to show as the author of this Best Practice.
Abstract *
Maximum file size: 1 MB
This will show on the archive page for the Best Practice.
OPFs *
Select 1 to 3 OPFs