ReST 3.0 – A lap around HTTP Apis' next generation
summary
Claims that "ReST 3.0" is practical not mythical: shows a toy API (ReadFlicks) with a home document linking to resource templates and reusable schema.org types, adopts a standard Problem Details error format, uses HAL/Siren-style forms and link headers (RFC 5988) for discoverability, and leverages HTTP/2 features—header compression, multiplexing and HTTP/2 preloading—to avoid N+1 round trips. Cites concrete tooling like AWS API Gateway and a BBC study reporting ~35% mobile speed improvement; demonstrations focus on interoperable schemas, caching, and unchanged clients.
AI-written summary · about
chapters (39)
- 0:00Intro
- 0:52Who am I
- 3:07Rest is dead
- 4:13The history of REST
- 5:29SOAP vs REST
- 6:11REST vs HTTP
- 6:51Hypermedia
- 8:46Following links
- 9:04Restrepo
- 9:41Is it restful
- 9:55No one cares
- 10:30Whats important
- 10:47Reinventing wheels
- 11:49Web vs RPC
- 13:00Uniform interfaces
- 13:34Tools
- 15:12Home Documents
- 17:20Code
- 18:06Problem Format
- 18:41Exception Handling
- 19:12Layering
- 20:54Orthogonal concerns
- 21:59Evolve systems
- 23:56Follow the links
- 25:20Discover all those leagues
- 27:48Link headers
- 30:03JSON
- 31:18Scaling
- 31:40Autonomous components
- 32:04Resources
- 33:13Caching
- 34:05Cache
- 35:48Transclusion
- 37:03HTTP to the roundtrip
- 38:28HTTP inefficiencies
- 39:00How much better
- 39:43The future
- 40:22Is ReST dead
- 40:34Outro
related talks
58mReST 3.0 – A lap around HTTP Apis' next generation
01h 04mThe Rest of ReST
52mREST: I don't Think it Means What You Think it Does
01h 39mLet’s have some Effective REST
37mREST, for real!
50mThe Fashion for REST - Creating Beautiful APIs
46mLet’s have some effective REST!
42mLet’s Have Some Effective REST!