~/talk

When to Use the API

Talkat WordCamp London 2018 · 2018-04-13..04-15· [api-design, nodejs]
links:none on file
slides:none on file

Argues when the REST API is worth the complexity by showing concrete builds: a Node.js ingest pipeline plus a cached content API to offload heavy imports; an Elasticsearch layer and an accelerator plugin that bypasses WordPress boot to cut API latency (example from ~5s to ~0.5s and another case reduced by two‑thirds); a Site-in-Numbers plugin that exposes big‑data JSON; a Team GB geolocation flow that splits the UK into four endpoints for performance; an Ionic CRUD app and experimental game engine using Gutenberg’s block model and transients for caching.

AI-written summary · about

  1. 0:00Start
  2. 0:40WHEN TO USE THE API
  3. 10:27API DELIVERY SYSTEM
  4. 13:27INTEGRATING SYSTEMS
  5. 32:08DEV RESOURCES
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 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
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
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.