API Governance in an Anti Governance World
summary
Argues that lightweight, automated governance prevents costly mistakes by running OpenAPI lint rules as part of CI/CD (run on commit or build via Jenkins), using Spectral-style JSON configs and IBM's open-source linter to enforce linting-as-code and custom rules. Gives concrete wins: catches wrong security profiles, missing examples, inconsistent naming, and embarrassing path mistakes; helps a client facing 6,500 APIs prioritize dead‑wood removal and incremental fixes. Recommends near‑instant feedback to developers, rule impact analysis, and quarterly rule reviews.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:40Chris Phillips Background
- 2:09Examples
- 3:30Marketing Slide
- 5:08What is Governance
- 15:30Sample Governance Rules
- 17:41Linting Tools
- 18:42JSON Configuration
- 19:25Build Process
- 22:55Benefits
- 23:56QA
- 32:55Tips
related talks
25mAutomating API Governance
26mAPI Governance: The Latest Trends Making Teams Love API Standardization.
26mAPI Governance - The Pursuit of Consistency
40mAutomated Governance in Practice
24mSelecting the best API Governance for your organization
26mContinuous API Governance Management
21mMastering API Design: Why Community Matters
50mAPI Government
