What we learned shipping an Order book depth map to a live desk
Every desk eventually argues about its order book depth map, and for good reason — it sits on the critical path between an idea and a filled order.
What an order book depth map actually does
At its core, an order book depth map solves one job: execution and market access. Everything else — the dashboards, the integrations, the marketing — hangs off that single responsibility.
When spreads widen and order books thin out, the gap between a good and a mediocre order book depth map shows up directly in your fill prices.
What to look for
When you put an order book depth map through its paces, weigh it against the things that bite in production rather than the ones that demo well:
- Latency and uptime during the most volatile sessions, not the calm ones
- Breadth of supported venues, instruments and order types
- Fee tiers, maker rebates and how they scale with volume
- Built-in risk controls: position limits, kill switches, max-order checks
- API parity — anything the UI can do, the API should do too
Common mistakes
The usual trap is optimising for the happy path. An order book depth map that looks great on a quiet Tuesday can fall apart the moment volume, volatility or fees spike — which is exactly when you need it most. Test it under stress, with adversarial inputs, and on the messiest data you can find.
The bottom line
Pick the order book depth map you understand well enough to debug at 3 a.m. during a market event. Cleverness you cannot reason about is a liability, not an edge.
