REST next level: Crafting domain-driven web APIs
summary
Shows how to stop mapping domain intent onto CRUD by returning hypermedia links that drive workflow, using Spring + Kotlin and Postman in live demos and the columbiad-express repo on GitLab. Claims hypermedia (ATOS/HATEOAS) lets the backend expose links for selection, booking, rebooking so clients cannot call endpoints out of order and adapters live in controllers. Demo includes a breaking change from query param bound → journeyIndex and how link-driven clients remain resilient. Slides and code provided.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 7:33Space-trip booking domain
- 14:21Problems with REST APIs
- 22:04Aligning APIs with business
- 35:44Richardson model & HATEOAS
- 47:31Domain-driven REST APIs
- 48:58Q&A
related talks
46mREST next level: writing business-oriented web APIs
56mDDD & REST - Domain Driven APIs for the Web
59mFrom CRUD to Hypermedia API with Spring
46mGet HATEOAS and Hypermedia right with Spring
47mHypermedia IRL
44mCrafting Great APIs with Domain-Driven Design
44mDesigning Hypermedia APIs
51mREST beyond the obvious – API design for ever evolving systems