2004-2024 : Two Decades of Web Services, A Retrospective
summary
Timeline traces soap RPC to REST and hypermedia, highlights Roy Fielding's REST constraints (layering, statelessness, caching, code-on-demand, uniform interface) and cites 24 years of core HTTP architecture. Notes AJAX (2005) → JSON-driven APIs, the explosion of ad hoc RPCs, then a return to links via HAL representations with link templates used on a ticketing platform (Leicester Square Theatre) so clients follow API-provided URLs instead of hardcoding them. Mentions formats (collection+json, JSON‑LD, Siren, UBER) and that hypermedia facades enable cross-system linking and evolution.
AI-written summary · about
chapters (4)
- 0:00Start
- 5:02ARCHITECTURAL STYLES AND THE DESIGN OF NETWORK-BASED SOFTWARE ARCHITECTURES
- 6:28a set of constraints
- 24:15LONGER TERM BENEFITS • Change location of resources • Evolve API in backwards compatible way
related talks
01h 02mHypermedia and the Rest of REST
33mDesigning RESTful Web Services
20mYour Http-based API is not restful
19mREST, SOAP, Hypermedia: When, why & how to use what
28mA History Lesson in Painful Industry Mistakes
30mThe internet of things challange:building APIs that last for decades
43mHow the Web Evolves with Hypermedia
43mThe Hypermedia API