Take the 2-minute tour ×
Quantitative Finance Stack Exchange is a question and answer site for finance professionals and academics. It's 100% free, no registration required.

I would like to know from those that have used FIX (with Simple Binary Encoding) for HFT compares with the current (proprietary) protocols in use that often vary per counterparty.

Interested in bandwidth utilization and development time differences. For example, do the various FIX engines (is there a list?) that support FIX SBE allow a software team to get to market quicker with their models than having to learn each proprietary trade protocol?

share|improve this question
1  
Not sure this is really a good question here. You might try to focus it a bit more. Which market, for example, are you talking about? Pros & Cons are not general across the entire universe of venues. For ex, you'd be hard pressed to find a more compact order entry protocol than OUCH, but doesn't mean its better. –  Louis Marascio Nov 25 '13 at 17:18
    
@LouisMarascio doesn't matter what market to me, anyone with any market experience is fine –  Nikos Nov 25 '13 at 21:33
3  
@Nikos, which fruit is the healthiest to eat and which will reduce the likelihood of ever getting sick? What do you think your doctor will reply when you ask him such question? –  Matt Wolf Dec 23 '13 at 15:40
    
@MattWolf He should say "God knows" –  Nikos Dec 23 '13 at 22:36
    
So, then specify where you look to connect to and I am sure you will get a whole lot more meaningful responses. Merry Xmas. –  Matt Wolf Dec 24 '13 at 0:01

2 Answers 2

This is a really confused question and the OP clearly doesn't work in this industry. Any connection to an exchange requires using the format the exchange has chosen. I.e., you don't get a choice.

That said, I don't know of a single exchange that allows order entry via SBE. CME Group will use SBE for their new market-data feed (replacing FAST compression), but that's it.

share|improve this answer

FIX has some known deficiencies. Repeating groups is one of them. It can be costly in terms of latency to parse repeating groups inside repeating groups, requiring recursive calls. I prefer protocols that send a first message signaling that N messages will follow with the group info.

FIX is also too verbose consuming too much bandwidth. For that they have come up with FAST which compresses FIX by a great amount but it is mainly used by the exchanges for market data, not order routing.

When we developed our FIX and FAST engine (CoralFIX), we focused on three things:

  1. It must have a very intuitive and easy-to-use API for fast turnaround when coding the connections to the exchanges.
  2. It must be low latency, designed from the ground up for speed.
  3. If it is a Java one it must leave zero garbage behind otherwise the GC will add unacceptable latencies and variance.

Disclaimer: I am one of the developers of CoralFIX.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.