that code is a bit better but as useless, you are going through loops and layers to build some very simple trading tasks. Seems you just learn how to program, playing with patterns rather than focusing on functions and utility of your code. This makes your whole system very clumsy.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
How does IB's API work with historical data?
- Thread starter MJM
- Start date
that code is a bit better but as useless, you are going through loops and layers to build some very simple trading tasks. Seems you just learn how to program, playing with patterns rather than focusing on functions and utility of your code. This makes your whole system very clumsy.
completely useless, as usual from you.
Sometimes there might be meaningless post.
Let me know if anyone was successful, hopefully using R/Python. Will be paid!!!
using a MoM like ZeroMQ or other opensource MQ is really not the best way to get a price feed
REST APIs are better equipped for that, a query type pull rather than an asynchronous push
This statement is incorrect for technical and practical reasons. Just for the record so any unsuspecting reader would not take it as real information. Please do your research on the topic.
what do you mean incorrect ? MoM for feeding quotes into your script is probably the worst way, even though a lot of people do it.
You are welcome to elaborate if you feel you have a better technical reason for wanting a MoM for quote feed.
You talking about price feed which is continuous stream of data with variable number of messages per slice of time. For all practical purposes all communications occur using sockets - both Zeromq and Rest in this case. Zeromq and Rest are running on top of sockets adding extra layer of programming overhead and serving different purposes. Zeromq is a message broker which can buffer messages and is fast but still has some overhead (desirable or not - one can implement it themselves) over raw sockets. Rest has the overhead of the Web protocol (HTTP) which is much more overhead than needed for servicing data feed and has the disadvantage of two way interaction (request - response) that is not really needed for fast streaming data. I do not know if Zeromq is best or worst for data feed but certainly Rest which uses HTTP protocol GET and POST is not better suited for handling streaming data with variable and unpredictable number of messages per second. Do your research.
You talking about price feed which is continuous stream of data with variable number of messages per slice of time. For all practical purposes all communications occur using sockets - both Zeromq and Rest in this case. Zeromq and Rest are running on top of sockets adding extra layer of programming overhead and serving different purposes. Zeromq is a message broker which can buffer messages and is fast but still has some overhead (desirable or not - one can implement it themselves) over raw sockets. Rest has the overhead of the Web protocol (HTTP) which is much more overhead than needed for servicing data feed and has the disadvantage of two way interaction (request - response) that is not really needed for fast streaming data. I do not know if Zeromq is best or worst for data feed but certainly Rest which uses HTTP protocol GET and POST is not better suited for handling streaming data with variable and unpredictable number of messages per second. Do your research.
Thanks but, due to my short knowledge on technical terminology, it will Not help meto understand.
After 5 or ten years later I believe everyone will be familiar with those, similar to that TradingWorkStation like IB is well spread in the last 10 years.
Although my area is close to computer, my time also valuable too, for learning the terminology. So if someone was successful to feed data, let borrow his time after pay with amount > my hourly wage.
Furthermore my personal logic does NOT require real-time feed, but every one-minutes data for roughly 400 equities.
Thanks again for Xerom and REST.
You talking about price feed which is continuous stream of data with variable number of messages per slice of time. For all practical purposes all communications occur using sockets - both Zeromq and Rest in this case. Zeromq and Rest are running on top of sockets adding extra layer of programming overhead and serving different purposes. Zeromq is a message broker which can buffer messages and is fast but still has some overhead (desirable or not - one can implement it themselves) over raw sockets. Rest has the overhead of the Web protocol (HTTP) which is much more overhead than needed for servicing data feed and has the disadvantage of two way interaction (request - response) that is not really needed for fast streaming data. I do not know if Zeromq is best or worst for data feed but certainly Rest which uses HTTP protocol GET and POST is not better suited for handling streaming data with variable and unpredictable number of messages per second. Do your research.
nothing wrong with my research, maybe you should investigate more on your side.
do you know the purpose of a MoM ? quote feeds are probably the worst application of such a technology. Query based tech are better fitted than MoM tech for such an application. As for overhead, I do not disagree, both are costly, but for most pre-trade applications that can kind of "high" cost is not that meaningful, so a REST query is perfectly acceptable and recommended to get quotes.
If you want speed and no delay, then it's not MoM, but direct streaming of data through the network pipe, a listener on the client side, and a pipe stream of quotes being emitted from the server side. After all, quote feeds are nothing more than a continuous ticker that is "printed" as trades happens.
Even a fast flat file ETL can do a better job than MoM. Actually, I think one infamous company is doing exactly that for the major Exchanges.
nothing wrong with my research, maybe you should investigate more on your side.
do you know the purpose of a MoM ? quote feeds are probably the worst application of such a technology. Query based tech are better fitted than MoM tech for such an application. As for overhead, I do not disagree, both are costly, but for most pre-trade applications that can kind of "high" cost is not that meaningful, so a REST query is perfectly acceptable and recommended to get quotes.
If you want speed and no delay, then it's not MoM, but direct streaming of data through the network pipe, a listener on the client side, and a pipe stream of quotes being emitted from the server side. After all, quote feeds are nothing more than a continuous ticker that is "printed" as trades happens.
Even a fast flat file ETL can do a better job than MoM. Actually, I think one infamous company is doing exactly that for the major Exchanges.
zeromq was originally designed to handle financial market data and then the project was extended for other uses. It was highly optimized for finance in the first place. This is not true for Rest.
highly optimized for finance ? what the heck does that mean ? do you mean market data ? if it was optimized for market data, it's still irrelevant. It's like saying a screw was optimized for a hammer. MQ is not the best tool for quote feeds.
again, using a stack to store information sequentially is not the best way to access that information effectively. And since it has an high overhead cost, it's hilarious to see some are still not able to figure it out that MoM is not fitted for that job. Seems to be a lazy solution.
REST is the future.
again, using a stack to store information sequentially is not the best way to access that information effectively. And since it has an high overhead cost, it's hilarious to see some are still not able to figure it out that MoM is not fitted for that job. Seems to be a lazy solution.
REST is the future.