Alternatives to Nanex

IAS_LLC, sounds like you are using shared memory within a C++ app across threads. Is that correct ?

What I have works between C++ and Java and am fairly confident in it continuing to work - the major effort now is to serialize NxCore's C++ structs (to shared memory/memory mapped file) and deserialize on the other end in Java. There are I think 50+ such structs; so I will probably write a code generator. Not a big deal, but it is still work if you know what I mean.

I run Linux and I am aware Wine can run NxCore just fine. So far, I've been using Nanex's native Linux client in samples and it worked just fine. Their real-time Linux native client is supposed to land in Q3 and I fully expect delays. Until then, the plan is to continue building the rest of my system.
 
jtrader33,
Was/is this a sticking point for you/someone ?

I only ran the sample historical application. Based on ping times to my local machine (near NY/NJ) (30 ms) and to my machine in the cloud in Iowa (10 ms), this historical data download server appears closer to Chicago than NJ. I can't say anything about the real-time server.

Yeah, I have one strategy that is latency sensitive and I would have switched to them if the equities data server was in NJ. They said it was in the works and I nagged them about it for a couple years (a few years ago), but eventually gave up. Since I'm always around 1000 tickers or so on any given day, I don't see much difference between NxCore and IQFeed once the data routes from NJ -> Chi -> NJ (my server). I always thought that was silly but I'm sure they have business reasons for it.

I also would have been more likely to switch if there was a java api, fwiw.
 
Thanks for the link. Execution is a way off yet and I am likely to start with IB. From a cursory look at Redi, details of the API appear fairly scant.

Redi has a FTP site for API docs. There are a lot of documents there. Contact them and ask for access. They might make you go through your broker.
 
Back
Top