Mastering API Design: Why Community Matters
summary
Argues that governance shifts from centralized committees to a community-led model: a small core team (often fewer than five for 20–30k companies) curates contributions while domain teams hold local authority. Recommends inner source practices so teams share and review OpenAPI specs, treats APIs as products with product managers involved, and automates checks with tools like Stoplight.io and automated linting (Spectral) to remove gatekeeping and lower friction.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:03Intro
- 1:20SOA Governance
- 4:12Decentralized Governance
- 8:18API First Governance
- 11:05Why APIs Fail
- 12:05API Reviews
- 14:19IT Governance Principles
- 17:05Governance Transparency
- 18:40Governance Automation
- 20:44Shameless Plug
- 21:09Q&A
related talks
24mSelecting the best API Governance for your organization
26mMastering API Strategies for Digital Transformation
26mContinuous API Governance Management
25mAutomating API Governance
26mAPI Governance: The Latest Trends Making Teams Love API Standardization.
40mAutomated Governance in Practice
36mAPI Governance in an Anti Governance World
21mScaling API Design