Lessons from the API Stewardship Journey in Azure
summary
Microsoft describes moving from late-stage reviews to an ongoing API stewardship program that embeds dedicated staff, training and GitHub-hosted REST API guidelines; teams use Spectral, Postman and the Swagger Editor to catch defects early. Policies include avoiding code-generation for OpenAPI, enforcing idempotency, consistent paging and resource shape across families, using an API gateway for routing and telemetry, date-based versioning via query strings and a three-year deprecation window. Hundreds of services ship with many still in preview; process reduces breaking changes.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:16REST APIs for the data plane of Azure Services
- 6:51Moving Earlier in the API Lifecycle
- 7:56Emphasize Providing Value Instead of Oversight
- 10:09Building API Guidelines.
- 13:14Infrastructure, Tools, and Process
- 20:09The Importance of API Stewardship
related talks
21mIntroducing The API Lifecycle
26mAPI Governance: The Latest Trends Making Teams Love API Standardization.
26mMastering API Governance: Microsoft's Blueprint for Success
01h 00mLessons from the API Management Trenches
25mAutomating API Governance
59mDriving better outcomes through API first development
38mAPI Mastery: from the Design to Development
28mAPI Productisation - shift RIGHT to Better Product Resilience