If you are a broker and are planning to provide API service that just don’t go with XTS. It’s a bunch of extremely poorly written code. If a professional trader wants to create an application based on that API, its utterly useless and slower than anything. My experience with Kambala has been complete opposite, while its not that clean looking, but funtionality wise, its above XTS/ODIN in all aspects.
I’ll give a few examples as to why I am saying this:
- Order, trade, positions feed is completely out of sync. You send an order, sometimes “Cancelled” status arrives before the fill (trade) events.
- All the valuable information is broken down into multiple feeds, which causes a unnecessary complications and unforeseen cases.
- Positions feed is sent before Order/Trade feed. (When it should be opposite, the most important information is in order/trade, and everything about the position can be deduced using those)
- OrderStatus is useless in case of Cancel/Modify rejections. Its very difficult to make out the actual order status in these cases.
- Way slower than Kambala.