Let’s have some Effective REST
summary
Shows how to design APIs by modeling first on paper, identifying participants and activities, grouping nouns into resources (items, carts, orders, customers) and mapping verbs to HTTP (GET for reads, POST to create, PUT/PATCH to update, DELETE for physical deletes), then validating flows with note cards. Emphasizes six REST constraints: client–server and stateless, layered system and caching with ETags and cacheable GETs. Recommends tools like Postman and curl, Swagger/AsciiDoctor for docs, and points to a GitHub proof‑of‑concept (spring store / friendly store) that uses event messaging, Kafka and TDD.
AI-written summary · about
chapters (12)
- 0:00Introduction and setup
- 6:13Agenda and core concepts
- 9:29Integration strategies
- 22:38API modeling process
- 27:59Defining participants and activities
- 34:36Defining resources and actions
- 39:18Resource mapping and naming
- 48:17Managing resource relationships
- 53:50Validation and requirements
- 57:49HTTP standards and codes
- 1:07:43Constraints and best practices
- 1:26:58Q&A session
related talks
46mLet’s have some effective REST!
54mEffective Design of RESTful APIs
42mLet’s Have Some Effective REST!
53mEffective Design of RESTful APIs
01h 34mDesigning a REST-ful API using Spring 3
50mThe Fashion for REST - Creating Beautiful APIs
51mREST beyond the obvious – API design for ever evolving systems
58m15 Best Practices for Designing Enterprise RESTful APIs in the Cloud