~/talk

Architecture Patterns To Enable Stateful Communication Over Stateless Serverless Apis

name:Wenbo Zhu
links:none on file
slides:none on file

Claim: stateless serverless functions can host long-lived, ordered streams by layering a lightweight session layer and session ID mapped to an in-memory store that holds logs and ordering metadata. Uses HTTP/gRPC/WebSocket transports, Firestore-style watch APIs and push services (Firebase Cloud Messaging) as comparisons; proposes primitives: session creation, durable session store, and a push function that notifies clients. Case study sketches a real-time chat prototype with sub-second latency goals; solution exists as internal infrastructure work, not yet a public, finished product.

AI-written summary · about

  1. 0:00Introduction
  2. 1:57Overview
  3. 4:03Incremental Delivery
  4. 5:34Case Studies
  5. 6:56Challenges
  6. 8:18Latency
  7. 9:40Higher level abstraction
  8. 10:04WebSocket API
  9. 10:50State of Art
  10. 11:56Killer and Hood
  11. 13:00Can we have both
  12. 13:25Case study
  13. 14:31Realtime chat
  14. 15:19Session primitive
  15. 16:41Message primitive
  16. 17:10How to generate a message
  17. 22:06Stateful Communication
~/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.