How to Minimize Coupling in API Production and Consumption
summary
Argues that loose coupling is the real test of a useful API, claiming APIs only deliver platform value when business and IT co-design scope, not when IT mirrors internal systems. Recommends building an internal API platform, designing scope from existing customer integrations, and using versioning patterns, extensibility reviews and resilience practices so consumers treat APIs as dependable dependencies. Offers practical artifacts: slides, a book, and an API consumption compass, and uses the concrete goal of dramatically reducing breakage from 10,000 to 1,000 consumers.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:02Value of Api
- 10:53Api's Are Not about Technology
- 12:04Api's Are Necessary but Not Sufficient for Digital Transformation
- 22:27Thoughts about Loose Coupling
- 24:25Technology Considerations
- 25:58Developer Culture
- 29:12Loose Coupling
- 31:06Final Speaker
related talks
27mUnlocking API Success: Bridging Business & Engineering
27mAvoid These API Design Mistakes for Better Business Integration
33mDesigning Sustainable APIs
49mBuilding Software Better: API Lifecycle Management for Developers
23mLeverage APIs to Transform Your Business Landscape
26mCollaborate Like You Mean it: The End of Siloed API Development
26mMastering API Strategies for Digital Transformation
26mRevolutionizing Business with API-First Strategy: Key Insights