Hot answers tagged order-handling
7
The "price protection" refers to RegNMS in the US. A stock exchange that does not have the best price must route all order flow to the exchange that does. The SIP in the figure is a consolidated feed that lists the best price among all exchanges.
Consider this example: a broker sends a market order to buy JNJ to NYSE where the best offer is \$86.97. ...
3
Louis's answer hints at the problem. Most market-data feed formats only use the order's reference ID for cancel, replace, or execute; they do not list the symbol or side. So you'll need a way to look-up the particular order by ID alone just to make adjustments. You can aggregate by price if your application requires it, but just know that the "level book" ...
3
The "correct" way is the way best suited to your trading. Regardless as to your data structure of choice, you have to maintain a list of all orders active on your book. That's because subsequent messages reference Order ID and you have to look up the corresponding order to determine the price level being acted upon.
Given that you have to maintain a ...
1
I have never implemented an order book, but I don't see immediate benefits from this aggregation. If you merge the volumes, then during the actual execution you'll have additionally to take into account that these orders came from different market participants. This seems to add additional complexity to your implementation.
From the point of view of market ...
Only top voted, non community-wiki answers of a minimum length are eligible
