Scaling API Design
summary
Argues that API programs start at the portfolio level: name and define capabilities from the customer perspective, then design resources; choose a spec and build mocking APIs so frontends and backends race together. Recommends a design-first step after portfolio, a dedicated client advocate to judge usability, bake versioning but aim to keep V1 (PayPal reports not turning off APIs in ~10 years), automate governance where possible, and notes 75% of capabilities moved from chaos into an organized REST portfolio this year.
AI-written summary · about
chapters (10)
- 0:00Introduction and platform
- 1:47API portfolio management
- 4:45Designing for capabilities
- 7:39Design-first methodology
- 9:38The client advocate role
- 11:34Versioning and standards
- 13:32Naming and flow design
- 15:34The Goldilocks principle
- 16:58Automation and evangelism
- 19:26Feedback and conclusion
related talks
26mMastering API Strategies for Digital Transformation
27mBuilding Great Web APIs
35mBuilding Your API for Longevity
26mRevolutionizing Business with API-First Strategy: Key Insights
30mConsumer APIs Must be Product-Driven
40mThe API mindset: tech, product, business and legal
33mDesigning Sustainable APIs
27mUser focused API Design