Enterprise Integration Zone is brought to you in partnership with:

As VP of Technology Evangelism at WSO2, Chris Haddad raises awareness of Platform as a Service, Cloud Architecture, Service Oriented Architecture, API Management, and Enterprise Integration. Prior to joining WSO2, Haddad’s experience includes building software development teams, contributing to open source, crafting technology roadmaps, leading Gartner research teams, and delivering Software as a Service and Web applications. Chris is a DZone MVB and is not an employee of DZone and has posted 111 posts at DZone. You can read more from them at their website. View Full User Profile

Defining an API Governance Approach

02.20.2014
| 3338 views |
  • submit to reddit

API governance is heavily influenced by IT business goals and objectives.  Leading API governance platforms provide analytics supporting the assessment of IT business value.  The platform should capture service tier subscription information, collects usage statistics, present productivity metrics, and integrate with billing and payment systems.

API governance encompasses API subscriptions and API promotion meta-data.  Governance activities managing API promotion meta-data include rationalizing keyword tags used to categorize APIs, and developer documentation content management. The governance process should enforce design-time checkpoints before API publication.

API Economy metrics include adoption and usage.  API governance establishes API adoption (by version, by API) and usage (by version, by API) processes, policies, and metrics.  By understanding API adoption and usage, API business owners and API architects can intelligently invest future development resources, properly plan API infrastructure scale, and rationalize the API portfolio.

Published at DZone with permission of Chris Haddad, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)