Binary Order Entry: Why Exchanges Left FIX
FIX is readable and flexible, but parsing text tag-by-tag costs microseconds that matter at the highest-speed venues — which is why many exchanges offer a second, binary order-entry protocol built purely for speed, alongside FIX for everyone else.
Prerequisites: FIX Message Types And The Tags That Matter
FIX messages are text: tag=value pairs separated by delimiters, human-readable in a log file and flexible enough to add new optional fields without breaking old software. That flexibility has a cost — a receiving system has to scan the message character by character, split it on delimiters, and look up each tag number before it knows what it's even holding. At normal trading speeds this overhead is irrelevant. At the speed the fastest market participants operate, where the difference between two competing orders can be measured in microseconds, that parsing overhead is exactly the kind of cost worth eliminating.
What a binary protocol does differently
A binary order-entry protocol — examples include Nasdaq's OUCH and CME's binary iLink/SBE — replaces text tags with a fixed, pre-agreed byte layout: byte 0 is always the message type, bytes 1 through 8 are always the order ID, bytes 9 through 12 are always the price, and so on, with no delimiters or tag numbers to parse at all. Both sides simply know the layout in advance and read fixed offsets directly out of the byte stream. There's far less to compute, and the messages themselves are smaller, which also shaves transmission time.
The trade-off is that binary protocols are venue-specific and rigid: because there's no self-describing tag structure, adding a new field generally means a new message version that every participant has to update to support, rather than an optional tag that older systems can simply ignore. FIX's flexibility, which binary protocols give up, is precisely what makes FIX easier to extend and to read while debugging.
Why both exist side by side
Most exchanges that offer a binary protocol also keep a FIX gateway running, because not every participant needs the extra speed and building a binary-protocol client is real engineering effort many firms don't want to spend. A firm chooses based on its own latency sensitivity: a market maker competing on speed for the same instrument as everyone else has a direct reason to build against the binary protocol, while a firm sending occasional institutional orders has little to gain from the added complexity.
Binary order-entry protocols trade FIX's text-based flexibility for raw parsing speed by using a fixed byte layout instead of tagged fields — exchanges that care about serving latency-sensitive participants typically run one alongside a standard FIX gateway rather than replacing FIX outright.
If you're ever choosing between a venue's FIX and binary gateways, the deciding question is whether your strategy is actually latency-sensitive relative to competitors trading the same instrument — the binary protocol's speed advantage is wasted effort to build against if nothing you do depends on winning a microsecond race.
Related concepts
Practice in interviews
Further reading
- Nasdaq OUCH Protocol Specification
- CME iLink / Simple Binary Encoding Documentation