REST: I don't Think it Means What You Think it Does
summary
Claims REST is an architectural style defined by Fielding’s constraints: use URIs for stable resource identity, exchange representations, and drive flows with HATEOAS rather than hardcoded paths. Practical advice: avoid version numbers in the URI (they force needless URI churn), expose a service document or resource-embedded links for discoverability, and publish machine-readable controls (URI templates, forms, media types like application/atom+xml, Collection+JSON, HAL or JSON Home). Real systems that add hypermedia controls reduce client coupling and let servers relocate or evolve endpoints without breaking clients.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:02identification of resources
- 6:12resource manipulation through representations
- 9:24hypermedia as the engine of application state
- 12:15self-descriptive messages
- 46:19Hypermedia types
related talks
21mThe REST API Myth
41mReST 3.0 – A lap around HTTP Apis' next generation
09mInterview: When Is RESTful API Design Useful?
58mReST 3.0 – A lap around HTTP Apis' next generation
50mThe Fashion for REST - Creating Beautiful APIs
42mLet’s Have Some Effective REST!
01h 02mHypermedia and the Rest of REST
40mWhat is REST? Why is it Part of the Rails Way?