Data Feed for Options on Futures
|December 12th, 2011, 08:08 AM||#11 (permalink)|
Futures Experience: Intermediate
Platform: Ninja, writing own now
Posts: 212 since Mar 2010
Thanks: 47 given, 101 received
No idea, but gfiven how dense they are - no Propietary.
You access them with a cll that uses shared memory to talk to a windows service doign the heavy lifting (recording ata etc.). You can have X different clietn conected to the same service.
The difference they have is that they dont deliver "data" but a "tape" which is a file per day. You can start "the real life tape" (playing back from the beginning or a named tape (path) which then plays back as fast as data is available (i.e. you process it). All incoming data iswriten to teh tape file, and all missing data, too. So, your tapes always are "current", and they backfill 2 weeks or so of tapes if you ahve a larger outage. One tape per day, even weekends (though the sunday is small, containing only very little data). Makes it easy to verify you have all data.
Tapes are not filtering - you get all data on the tape, you ahve to filter in the app or via plyback flags (do not show me level 2, for example).
I find the API very dense - not in a negative sense. The also provide a ton of reference data, for example trading times some days in advance, which you can use to feed core control (get out before market closes).
They are generically hard to get going with a retail software system because of their way to handle data. The MF tape has up to about 3 million I think (extremes) updates per minute, normally around 250.000. This just is a ton of stuff there.
Now, liquidity - another story BUt not NxCores problem.