The Western Devs discuss the ins and outs of building APIs
Recorded on Friday, March 11, 2016
Synopsis
- What is an API?
- Clarifying "public" with respect to APIs
- Why build an API?
- APIs as a means of breaking down components and compartmentalizing data
- API design considerations
- The effect of microservices
- Versioning an API
- Maintaining multiple versions
- Using a message upgrade service
- Only adding to the API
- The cost of maintaining backward compatibility
- Using speed as an incentive to get customers to upgrade to a later version
- SignalR/Websockets
- Balancing data between an API and a webhook
- Services that integrate with APIs (e.g. IFTTT, Zapier)
- Native integration with 3rd party services
- Authentication
- Token-based
- OAuth2
- Application-specific tokens
- Expiring tokens
- Applying permissions to tokens