Selecting the best API Governance for your organization
summary
Argues that API governance must balance centralized standards and decentralized delivery, gives concrete artifacts to create: developer portal, published APIs, and a test environment with whitelisting and automated plus human checks for partner onboarding. Recommends a RACI-style body to manage lifecycle actions (create, publish, maintain, retire), weighs costs of strict enforcement against lost innovation, and cites Amadeus as an enterprise example and the book Continuous API Management as practical further reading.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:58What is Governance?
- 5:13Challenges
- 7:46The API Life Cycle
- 10:07Small Scale
- 11:03Medium Scale - Multiple teams
- 11:51Large Enterprise
- 13:42Governance definition revisited
- 15:16Artefacts
- 18:38Partner Onboarding Process
- 20:57Who decides traditional enterprise example
- 22:05API Governance at Amadeus
related talks
26mContinuous API Governance Management
27mPillars of the Successful API Governance
50mAPI Government
21mMastering API Design: Why Community Matters
25mBeyond API Governance: Run your API org like a lean startup
40mAutomated Governance in Practice
02mThe Flawed Logic of Universal API Governance in Large Enterprises
26mWhy Your API Governance Fails at the Operating Model