APIs for Scaling Enterprises: Setting and Applying API Standards.
summary
Argues that scale requires a company-wide OpenAPI schema plus an linter baked into CI/CD that enforces casing, strong typing and tooling-compatible fields; recommends an API council to set standards, central reuse models instead of per-team variants, and a single common API gateway for unified rate limiting and analytics. Mentions Stoplight, Swaggerhub, Swagger Inflector, openapi-diff and codegen quirks and reports these measures prevent brittle integrations and reduce transformation code.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:24Principles of API Design
- 3:52Design First API
- 9:02Establishing API Standards
- 10:45API Council
- 12:22The Linter
- 14:39Sharing Models
- 16:52Be Prepared
- 19:10API Gateway
- 20:34Future of APIs
- 21:35Extra creative tools
- 23:04Audience QA
related talks
26mAPI Governance: The Latest Trends Making Teams Love API Standardization.
28mThe New API Stack
14mHow to build better and consistent APIs at scale
28mMaximize API Growth: Strategies from Industry Experts
25mAutomating API Governance
26mGrowing an API Culture
27mEnterprise API management in agile integration
24mSelecting the best API Governance for your organization