The Fashion for REST - Creating Beautiful APIs

on YouTube ↗50m

" summary

Defines what RESTful means by detailing the Richardson Maturity Model and concrete HTTP semantics (GET/POST/PUT/DELETE/OPTIONS) and status codes, including using 202 Accepted for asynchronous work and HATEOAS via hypermedia links. Uses concrete examples—a Tesla Model S REST-style API, a photo-tagging service that incorrectly used GET for side effects, and a GitHub gist showing async tasks that return a result resource—and recommends vendor media types for versioning while advising to use RPC when endpoints are truly command-style.

AI-written summary · about

" chapters (15)

1. 0:00Introduction to REST
2. 1:05What REST really is
3. 3:20REST vs Chinese schools
4. 5:33Roy Fielding and REST
5. 6:57REST principles
6. 10:32Level 0: XML-RPC
7. 11:34Level 1: URI identifiers
8. 13:40Level 2: HTTP methods
9. 17:14REST API examples
10. 21:32HTTP status codes
11. 28:04Level 3: Hypermedia links
12. 36:17REST vs API docs
13. 39:48Beyond CRUD in REST
14. 44:06Content-Type and versioning
15. 47:39REST versus RPC

" related talks

• 01h 39mLet’s have some Effective RESTMohamed Taman · Global Summit for Java Devs 2020
• 53mDomain-Driven RESTTomek Cejner · Confitura 2019
• 54mEffective Design of RESTful APIsMohamed Taman · Oracle Code One 2018
• 52mREST: I don't Think it Means What You Think it DoesStefan Tilkov · GOTO Amsterdam 2014
• 46mLet’s have some effective REST!Mohamed Taman · Voxxed Days Bucharest 2022
• 33mDesigning RESTful Web ServicesDavid Zuelke · APIdays Paris 2012
• 40mWhat is REST? Why is it Part of the Rails Way?Javier Ramirez When David Heinemeier · RailsConf 2014
• 42mLet’s Have Some Effective REST!Mohamed Taman · JCON Europe 2023