Kin Lane
API Evangelist
IBM Impact
April 2014
- Some Quick Background On Myself...
- 25 Years Database Engineer
- 15 Years Web Applications
- 8 Years Cloud Computing
- 4 Years Studying APIs
Focus
- Technology of APIs
- Business of APIs
- Politics of APIs
Target
- Individuals
- Startups
- SMB
- Enterprise
- Government
History of APIs
History of APIs
Commerce
- Salesforce (CRM)
- eBay (Auctions)
- Amazon (Products)
- Paypal (Payments)
History of APIs
Social
- Flickr (Images)
- Delicious (Bookmarks)
- Twitter (Posts, Friends, Images, etc)
- Facebook (Posts, Friends, Images, etc)
History of APIs
Cloud / Infrastructure
- Amazon S3 (Storage)
- Amazon EC2 (Compute)
- Amazon SimpleDB (Data)
- Amazon RDS (Database)
History of APIs
Mobile
- Instagram (Photos)
- Foursquare (Local)
- Pandora (Music)
- Twilio (SMS)
History of APIs
Why Is It Working?
- Built on HTTP
- Simplicity
- Light-Weight
- Hackable
- Distributed
- External / Internal
- Pay For Use
History of APIs
Three Essential Ingredients
- Social
- Cloud
- Mobile
Business of APIs
Business of APIs
Self-Service
Business of APIs
Documentation
Business of APIs
Code Samples
Business of APIs
Communication
Business of APIs
Access Tiers
Business of APIs
Showcase
Business of APIs
Analytics
Business of APIs
Embeddable
API Politics
Politics of APIs
Terms of Service
Politics of APIs
Privacy Policy
Politics of APIs
Service Level Agreements
Politics of APIs
Support
Politics of APIs
Code License
Politics of APIs
Data License
Politics of APIs
Rate Limits
Politics of APIs
Availability
Politics of APIs
Roadmap
Politics of APIs
Changelog
Politics of APIs
Deprecation
Politics of APIs
Budget
What Can We Learn?
Maximize Interoperability
Increase Access To Resources
Increase Organizational Agility
Quantify Resource Usage
Define New Products
Recover Operating Costs
New Revenue Streams
Empower Partners
Changing Culture!
The End
By Kin Lane (@kinlane)
