What "real-time" actually means here
The phrase is used loosely, so here is the mechanism. A fill lands over a persistent connection with per-source sequence numbers, gap detection and resync. The book applies it as an event rather than overwriting a snapshot. A risk engine running off the request path revalues exposure, margin, collateral and limits across the whole book, and the result is pushed to every open screen over a live stream with a polling fallback. The browser displays; it never calculates. Nobody presses refresh and nobody waits for a page to reload.
- Streaming ingestion — WebSocket with sequence gap detection, FIX drop-copy, NATS
- Event-sourced book: corrections are appended as events, never silent overwrites
- Whole-book revaluation on a continuous loop, off the request path
- Results pushed to every client over a live stream, with a polling fallback
- Continuous mark-to-market against live venue prices