The Secret to a Successful API is Internal
summary
Argues that success starts internal-first with inventorying content, owners and business rules, not with a sexy public launch; cites Amazon mandating web services in 2003–04 that seeds AWS (S3 in 2006 began as CLI/web API) and an affiliate network of ~1,000, and Netflix breaking services into APIs to support ~700 devices where the public API is ~0.05% of traffic; prescribes HTTP web APIs, self-service access and a decouple resources approach plus clear deprecation/communication and self-service governance.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:33The Secret to a Successful Api Is Internal
- 2:00Why Were Web Apis Successful
- 4:00Apis Start Internally
- 4:34Identifying the Relationships
- 7:55.So Examples of Internal Api Success
- 12:39How Can Apis Transform How Your Company Operates
- 18:48Api Evangelism
related talks
24mDesigning the APIs for an Internal Set of Services
29mAdapting to an API Enabled World (Panel Debate)
41mWhy your company needs an internal API and what you should do about it
18mWinning in the API economy
49mWhy you need an API, and what to do about it
21mPragmatic Strategies for Global API Integration
02mThe Flawed Logic of Universal API Governance in Large Enterprises
26mFrom project to reality let's explore some API