Let’s have some effective REST!
summary
Shows a concrete modeling workflow: identify participants → list activities → map to resources → revise → define API, applied to a telecom MVNO product and validated with paper prototypes and note cards. Recommends three migration patterns (brownfield, greenfield, facade), maps resource lifecycles to HTTP verbs, uses ETags for caching and JWT for stateless auth, and limits response codes to a small set (200, 201, 202, 204, 301/302, 404, 500). Proofs and examples live on GitHub and are production-proven.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 6:39Design
- 10:54API
- 14:50Three Rules
- 16:05Identify Participants
- 19:22Consistent Process
- 20:18Create API Definition
- 21:30Mapping Activities
- 24:28Designing Relationship
- 27:12Validate
- 29:02HTTP
- 30:14REST API
- 31:37Stateless API
- 33:52Caching
- 36:16Layer system
- 37:55Cache on demand
- 38:58Uniform interfaces
- 43:14Conclusion
