Imported from previous forum
I have been browsing FIXprotocol site out of interest for couple of months, but I have no Finance background (but I have server programming exp.)
Given so many FIX engine out in the market, would it make sense to develop a new product, and what would be the “killer feature”?
I have been thinking if “low latency”, “fault tolerant” & “number of simulataneous connections”, could make a difference, and if so can get these figures for best FIX engine in the market.
Any other ideas for improvements that is lacking in current FIX engines around?
Thanks,
Nick.
I have been browsing FIXprotocol site out of interest for couple of
months, but I have no Finance background (but I have server
programming exp.)Given so many FIX engine out in the market, would it make sense to
develop a new product, and what would be the “killer feature”?I have been thinking if “low latency”, “fault tolerant” & “number of
simulataneous connections”, could make a difference, and if so can get
these figures for best FIX engine in the market.Any other ideas for improvements that is lacking in current FIX
engines around?Thanks,
Nick.
Hi Nick,
You’re right about the fact that there are a number of different commercial FIX engines available. There are also several open-source projects out there - most notably the QuickFix projects.
In the context of open-source or non-commercial offerings, I would suggest that a great idea would be the development of a new fix engine that targets the .NET platform. We already have QuickFix/J out there, which provides great functionality on the Java side of the world, but on the C#/.NET side of things the best we seem to have right now is the C# bindings that are supported by the QuickFix/C++ project.
Considering the number of firms that are adopting .NET for trading applications, I think this would be an excellent time to start an OSS project to develop a .NET/C# FIX engine.
Otherwise, I’d probably say that considering the number of excellent commercial engines that are already available, you might have more fun developing interesting new tools that support FIX rather than trying to build yet another FIX engine…
more fun developing interesting new tools that support FIX
Would you please suggest a new tools which would be interesting and you suppose there would be a demand for?
more fun developing interesting new tools that support FIX
Would you please suggest a new tools which would be interesting and you
suppose there would be a demand for?
Hi Constantine,
Sorry for the late reply, I just read your post. I think there are a number of areas where new and innovative tools would be useful. The FIX protocol is used in so many different types of financial systems, that the palette of applications/tools you could choose to build is just tremendous. Half the fun of developing something new is coming up with something that isn’t available, especially in the OSS space, so I would recommend you take a look at commercial offerings and then see if you could put a new spin on something…
more fun developing interesting new tools that support FIX
Would you please suggest a new tools which would be interesting and
you suppose there would be a demand for?Hi Constantine,
Sorry for the late reply, I just read your post. I think there are a
number of areas where new and innovative tools would be useful. The FIX
protocol is used in so many different types of financial systems, that
the palette of applications/tools you could choose to build is just
tremendous. Half the fun of developing something new is coming up with
something that isn’t available, especially in the OSS space, so I would
recommend you take a look at commercial offerings and then see if you
could put a new spin on something…
It would be good if we get a message when there is a post
to subscribed thread.
How can I begin development of FIX engine - the question
is how it can be tested?