Senior Backend Engineer / Stage 3 · APIs

Select polling, SSE or WebSockets for updates

Demonstrate disconnect and resume.

Choose oneIntermediateDraft, not yet reviewed15 min of activities

"Already know" meets prerequisites. "Not relevant" removes the topic from your total but leaves what builds on it waiting.

Self-check

  • You display order-state updates and accept changes through ordinary HTTP requests. Choose a transport. After receiving event 41, disconnect, generate events 42 and 43, and reconnect. Explain how your server decides what to replay and what happens when 41 is older than retention.
  • Evidence to include: State a cursor format, duplicate policy and bounded-buffer policy. Distinguish the browser reconnect mechanism from your application's replay guarantee. A diagram or local fixture is sufficient; a live hosted socket service is unnecessary.

Try it without the material first, then compare. Save your answer in your notes below. Report a problem with this self-check

Learning activities

2 activities
  • Not done
    Using server-sent events (opens another site)
    ReadOther sitelink checked 2026-11-15

    How a browser receives a one-way event stream, with the id and retry fields that control reconnection. It does not cover replay on the server; the self-check does.

    10 min
  • Not done
    WebSocket API (WebSockets) (opens another site)
    ReadOther sitelink checked 2026-11-15

    A short overview of two-way sockets, including the warning that the WebSocket interface has no backpressure, which matters when choosing a transport.

    5 min

My notes

Saved on this device, synced when signed in
Esc
↑ ↓ to move↵ to open