What Makes an Agile API?
summary
Beepsend describes concrete lessons: avoid reinventing the wheel by outsourcing noncore features and gain customers through Zapier integration and partners like Pingdom and Podio; treat APIs as productized documentation using RAML-first documentation or Swagger; combine relational, NoSQL and key-value stores (Redis) where appropriate; automate security and centralized configuration to survive CVEs like Heartbleed and POODLE and forced MySQL upgrades; watch integer overflow risks (Twitter migration); use CI and test beds, keep SLAs simple, and measure what actually breaks.
AI-written summary · about
chapters (8)
- 0:00Start
- 8:00MISCONCEPTION #2
- 10:09MISCONCEPTION #3
- 15:40MISCONCEPTION #5
- 16:30MISCONCEPTION #6
- 19:54AGILE TIP #1
- 22:02AGILE TIP #3
- 22:33AGILE AGILE TIP #5
related talks
38mAPI Mastery: from the Design to Development
22mAPI and Platform Strategies to Win in Global and Local Markets
20mPotential of API integrations, common traps and advices
43mAPIs Are the Backbone of Every Company
31mThe API in 2017
45mAgile API Development, Bringing Testing and Development Together
27mBuilding Great Web APIs
49mBuilding Software Better: API Lifecycle Management for Developers