Designing a REST-ful API using Spring 3
summary
Design shows concrete choices: use Spring 3 MVC controllers, Jackson for JSON, and Rest Shell for manual demos; return 201 with a Location header when creating games and 202 for long tasks; model actions as state changes (PUT a door’s status) instead of inventing verbs; expose navigable HATEOAS links produced by resource assemblers so clients never hardcode URIs; test the web layer with MockMvc tests to assert status codes, JSON payloads and link relations.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 1:24What is REST?
- 10:55HTTP verbs and their use
- 20:56Designing the API interaction model
- 30:51Implementing with Spring MVC
- 45:01Status codes and error handling
- 54:18Hypermedia and HATEOAS
- 1:11:04Spring HATEOAS and links
- 1:20:56Testing REST APIs
- 1:27:17Q&A and summary
related talks
01h 39mLet’s have some Effective REST
54mEffective Design of RESTful APIs
53mEffective Design of RESTful APIs
42mLet’s Have Some Effective REST!
51mREST beyond the obvious – API design for ever evolving systems
01h 23mDocumenting RESTful APIs
46mLet’s have some effective REST!
56mDDD & REST - Domain Driven APIs for the Web