Design and Build Great Web APIs
summary
Argues for a repeatable API-first workflow: design (story, diagram, ALPS description), build (sketch with API Blueprint, prototype with OpenAPI, implement in Node/Express), and release (Postman automation, Postman/Newman, OAuth0 tokens, Heroku staging with rollbacks). Shows how ALPS generates multiple specs and how prototypes catch contract gaps before costly code. Notes about ALPS and that HTTP has about 40 methods (but only a few are used). Recommends side-by-side versioning and preserving old tests to avoid breaking consumers.
AI-written summary · about
chapters (7)
- 0:00Introduction and overview
- 12:46Designing APIs step by step
- 27:56Building APIs with sketches and prototypes
- 37:01Implementing APIs with the Dart model
- 47:38Testing, security and deployment
- 55:21Modifying and maintaining APIs
- 1:06:21Q&A and closing remarks
related talks
24mProviding a childcare service for your API
40mCrafting Elegant APIs with Laravel
11mLifecycle of an API design
14mHow to build better and consistent APIs at scale
30mFrom futons to functions: the principles of good API design
41mPlanning a Front-end JS Application
32mLet's put U in UX!
39mAdventures in APIs