The REST API Myth
summary
Argument: Fielding's dissertation defines architectural constraints not an API style, and the common REST myth misattributes HTTP design advice to him. The concrete claim is that REST's value today is self-descriptiveness and stateless interactions, not URL verb prescriptions. Evidence: migrating CORBA/XML aggregation to plain HTTP yields readable metadata and works better with caching and layering. Tooling example: ELK dashboards plus HTTP/2 or HTTP/3, contract-first specs and code generation. Decision rule: pick REST when REST is about architectural constraints and explicitness matters.
AI-written summary · about
chapters (9)
- 0:00REST API myth
- 1:09Roy Fielding on REST
- 4:23API design history
- 8:42Dot-com era APIs
- 11:53REST principles impact
- 15:26Modern RPC rise
- 17:52REST in 2024
- 19:59Modern REST rules
- 21:03Q&A
related talks
52mREST: I don't Think it Means What You Think it Does
09mInterview: When Is RESTful API Design Useful?
22mAre REST APIs Still Relevant Today?
01h 02mHypermedia and the Rest of REST
51mREST beyond the obvious – API design for ever evolving systems
01h 01mAn Architect's Approach to API Strategies
42mLet’s Have Some Effective REST!
01h 39mLet’s have some Effective REST