~/talk

Let’s Have Some Effective REST!

slides:none on file

Covers concrete rules: identify participants and activities, map activities to verbs and expose resources as plural nouns, paper-test the API contract before coding, and validate with test plans. Explains three migration strategies—brute‑force, greenfield, facade—and gives a real example: wrapping a COBOL pension backend with a plugin to expose REST for a mobile app (worked). Recommends specific HTTP practices: use HEAD to check existence, standard codes (200/201/202/204/404), and ETag caching, plus stateless auth (JWT/OpenID) and HATEOAS links.

AI-written summary · about

  1. 0:00Intro
  2. 3:00Agenda
  3. 5:40Three Approaches to API
  4. 10:30Adding an API
  5. 14:20Design Process
  6. 21:03API Definition
  7. 27:53Relationship between resources
  8. 30:53Validate API
  9. 32:33Why HTTP
  10. 36:48Why REST
~/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.