What "real-time" actually means here
The phrase is used loosely, so here is the mechanism. Venue prices arrive over WebSocket, so a move reaches the book in milliseconds rather than on the next poll. A price move triggers a revaluation of the whole book — exposure, margin, collateral and limits — throttled to about a second and self-limiting, so the screen reflects the market roughly as fast as a person can read it. Fills land over a persistent connection with per-source sequence numbers, gap detection and resync, and the book applies them as events rather than overwriting a snapshot. Results are pushed to every open screen over a live stream with a polling fallback. The browser displays; it never calculates.
- Prices streamed over WebSocket, with a REST sweep behind it as reconciliation
- Revaluation triggered by price moves, not only by a timer
- Streaming ingestion of fills — WebSocket with sequence gap detection, FIX drop-copy, NATS
- Event-sourced book: corrections are appended as events, never silent overwrites
- Results pushed to every client over a live stream, with a polling fallback