Designing the APIs for an Internal Set of Services
summary
Argues that API design succeeds on concrete contracts not platitudes, shows a working cloud platform shiteru and a microservices stack using Ruby/Rails, Python, Tornado Web Server, Nginx, Java and JavaScript, adopts JSON Schema for schemas, and recommends consumer tests via consumer-driven contracts. Enforces a small set of meaningful HTTP statuses (e.g., 400, 401, 403, 404, 504), supports at least one prior version during migrations, and gives deployment and testing patterns that scale.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:20What is an API
- 4:48API Model Phase
- 8:11What makes a great API
- 10:47Errors
- 12:45Support
- 14:49Versioning
- 16:10Communication
- 20:58Deployment
- 22:23Tests
related talks
35mPrinciples of Awesome APIs and How to Build Them
35mBuilding Your API for Longevity
27mUser focused API Design
22mThe dirty secrets of building large HTTP APIs
28mSOA and APIs : Fearless Lessons From The Field
35mBroken APIs Break Trust: Tips for Creating and Updating APIs
04mReal-World Enterprise REST API Design
26mBuilding Scalable Microservice APIs From The Beginning