Developer-first APIs: the new norm of API Management
summary
Starts with Pokémon Go being reverse-engineered API via man‑in‑the‑middle and GPS spoofing that bypasses region locks and floods servers, prompting certificate pinning broken in four days and legal account suspensions. Moves to concrete API management practices: enforce rate limits and quotas, mutual SSL/OAuth, versioned graceful deprecation, and shield back-ends. Covers developer-facing work: developer portal and SDKs, test consoles, CI/CD and analytics to detect misuse and improve APIs.
AI-written summary · about
chapters (16)
- 0:00Start
- 7:25Who is the 'immediate' API consumer?
- 8:02The developer ecosystem in the API world
- 9:23Open your APIs, but make them safe!
- 10:23Handle changes gracefully
- 10:38Govern your APIs
- 11:33Shield against heavy traffic
- 12:06Design to scale
- 12:53Team collaboration
- 13:44Combine API + devops excellence
- 14:18Provide the right toolset
- 14:43Create a feedback loop
- 15:44Make your APIs informative
- 16:09Make your APIs easy to use
- 17:00APIs that are easily testable
- 17:35Build a community
related talks
25mAPI Security Deep Dive: Safeguard Your Digital Assets
38mAPI Mastery: from the Design to Development
30mAttack API Architecture
51mThe Next Application Security Frontier: AI-Ready API Defense
27mLatest Trends in API Management in 2019
28mMaximize API Growth: Strategies from Industry Experts
20mThe Dark Side of Managing APIs as a Product
20mPotential of API integrations, common traps and advices