Loading...
Loading...
Browse 5 real-world technical and behavioral interview questions about Low latency. Review scenarios, edge cases, and architectural best practices.
Designing an ultra-low latency distributed lock manager, evaluating consensus algorithms, and handling clock drift in high-frequency environments.
An authoritative breakdown of horizontal matchmaking services, constraint relaxation algorithms, and distributed locking for ticket-based lobbies. Use this matchmaking answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects SBMM to the point an interviewer is testing.
An order book is price levels in price order, each holding a time-ordered queue of orders, plus an ID index so a cancel is O(1); the hard parts are that cancels dominate the flow, the feed must be gap-checked and recoverable, and replay must be deterministic and allocation-free. It also connects matching engine to the point an interviewer is testing.
Pre-trade risk checks must stay on the order path without adding unacceptable latency. Keep static checks in-process, maintain bounded counters for local exposure and grant budgets for global limits, with a kill switch that fails safe. It also connects market access to the point an interviewer is testing.
Kernel bypass moves packet handling into user space so a market-data read no longer pays a syscall boundary, a kernel-to-user copy, interrupt and softirq handling, or a scheduler wakeup. You pay for it with a core burned on busy-polling, the loss of standard network tooling, and a driver-specific build. It also connects networking to the point an interviewer is testing.