~/talk

Effective Design of RESTful APIs

Talkat JavaDay Kyiv 2015 · 2015-11-06..11-07· [api-design, software-architecture]
slides:none on file

A concrete workflow: identify participants, list their activities, break those into resources (nouns) and map to HTTP verbs, then validate before coding — this prevents missed cases like partial cancel or reorder. Three integration strategies appear: bolt-on, greenfield, facade. Examples include a coffee shop and online book ordering; URLs for cart operations use nested resources (/carts/{id}/items/{id}), and CRUD maps to GET POST PUT DELETE. Validation uses HTTP features: status codes, headers, ETag caching and HATEOAS links.

AI-written summary · about

  1. 0:00Introduction to API design
  2. 2:13Modeling fundamentals
  3. 7:14API strategy selection
  4. 11:12Defining participants and goals
  5. 17:08Resource mapping
  6. 23:04Designing relationships
  7. 28:37Validation and refinement
  8. 33:32HTTP protocol concepts
  9. 36:39HTTP headers and status
  10. 40:03Rest architectural constraints
  11. 48:47Uniform interface and HATEOAS
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.