Live12 DBInside the v3 change-stream
The /v3/api/stream endpoint exposes a server-sent feed of
revision events. Each event carries a per-region revision id so consumers can
reconcile their local copy without a full snapshot.
Events are emitted per dataset — timezones, countries, currencies and
calendars — and ordered by a monotonic sequence number. Clients resume from the
last id they processed using the standard SSE Last-Event-ID header.
Under the hood, regional nodes replicate continuously; the stream is a thin projection over that replication log, filtered to the caller's edge region.
Because each event is small and self-describing, a consumer that falls behind
can either replay from its last seen id or fall back to a fresh snapshot from
/v3/api/snapshots and resume the feed from there. There is no hidden
server-side state per consumer — the cursor lives entirely with the client.