Effective Design of RESTful APIs
summary
Gives a concrete five-step API design: identify participants, list their activities, paper-model resources, map actions to nouns and HTTP verbs, then validate and iterate; uses coffee-shop and book-store examples and produces a small URL/verb spec on paper or Word. Emphasizes using Postman or curl to inspect headers, sticking to a few HTTP status codes, and the six REST constraints (stateless, cacheable, uniform interface). Advises minimal centralized documentation and filling gaps before coding.
AI-written summary · about
chapters (21)
- 0:00Intro
- 3:06Three approaches to adding an API
- 7:08Bolt-On Strategy
- 7:46Takes advantages of existing code and systems.
- 8:04Greenfield Strategy
- 8:57Facade Strategy
- 9:54Wraps existing logic, replace as you go.
- 10:38Tips for modeling APIs
- 12:25Don't worry about the tools.
- 19:18Creating & Grouping API methods
- 20:18Review last Challenge: Identifies participants and activities to order book online?
- 20:41Create API definition
- 23:16Mapping our Activities to Nouns & Verbs
- 23:33Map Actions to HTTP Nouns & Verbs.
- 26:58Mapping remaining Activities to custom actions.
- 33:32HTTP Overview
- 35:06REST is a generally agreed upon set of principles or constraints.
- 44:46Caching and Cacheability
- 46:57Layered systems
- 48:08Code On Demand Optional
- 49:21Uniform Interfaces
related talks
53mEffective Design of RESTful APIs
01h 39mLet’s have some Effective REST
42mLet’s Have Some Effective REST!
15mHow to Design Effective APIs | Actionable Guide
46mLet’s have some effective REST!
42mREST API design good practices
51mAPI Design in Real Life: What You Don't See in Books
48mRESTful API Patterns & Practices