~/talk

We Live in Memory: Making Λ and GraphQL Respond in 70MS

Talkat JSConf US 2018 · on Thursday, 2018-08-23· [serverless, databases]
slides:none on file

Claims a production GraphQL API runs at 70ms average (most requests ~24ms), cuts ops cost from ~$30k/month to ~$3k, and stays stable under spikes. Implementation uses serverless GraphQL on Lambda, Fastly CDN edge caching, and Redis as primary datastore with an append-only log and RDB snapshots. A custom graph layer (Gradius) and in-progress Nemesis DB power labeled-edge lookups, batching and pipelining, and the stack demonstrably works in production.

AI-written summary · about

  1. 0:00Intro
  2. 0:43We Live in Memory
  3. 2:46Goals
  4. 5:42Functions
  5. 7:30API
  6. 8:32Database
  7. 15:13Nemesis DB
  8. 16:53GraphQL Server
  9. 21:01GraphQL Resolvers
  10. 22:51Data Loader
  11. 25:07Lambda Deploy Tools
  12. 26:30Redis
~/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.