REST next level: writing business-oriented web APIs
summary
Shows using HATEOAS hypermedia links in JSON APIs to preserve domain intent and encapsulate workflows so clients don’t hardcode URLs or parameter names. Demonstrates a Spring-based space-train booking app tested with Postman where link-driven actions (select, get compatible returns, create booking) adapt when backend parameters change, and reports the technique has run in production for over three years preventing front-end regressions while surfacing business semantics.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:43Impedance mismatch in REST
- 8:58Application demo
- 13:39REST misconceptions
- 20:00API model vs business model
- 23:28Encapsulation breach
- 31:11Richardson maturity model
- 36:49Hypermedia controls deep dive
- 43:08Advantages and conclusion
related talks
51mREST next level: Crafting domain-driven web APIs
49mFrom CRUD to Hypermedia APIs with Spring (RU)
59mFrom CRUD to Hypermedia API with Spring
46mGet HATEOAS and Hypermedia right with Spring
21mBuilding Flexible APIs with Spring HATEOAS
55mFrom REST to Hypermedia APIs with Spring
47mHypermedia IRL
44mDesigning Hypermedia APIs