>The terminal is extremely slow most of the time and constantly crashes
Ok your comment is mindboggling to me. Having used Bloomberg for nearly 10 years, not only for the front-end but the back-end API I can tell you it is the most stable piece of software I've ever seen. Not once, not onesingletime has it crashed in those 10+ years for us. The API is even more impressive- to my knowledge we never even experience a single missed query or randomly dead data stream over all those years.
The terminal is expensive as hell, but they deliver on the cost.
Also just by the fact of how it's used, saying it constantly crashes and assuming it's just like that and traders are ok with that all day long? Whatever experience you seem to have must be an extreme outlier.
>It’s basically a giant piece of legacy code.
Eh I think that's silly. You even say it's designed for the power users, which is absolutly right. That's the only reason you think it's legacy. Are you telling me everything behind and their back-end is not extremely advanced? It has to be to support the amount of data that is flowing through them at every second in data that HAS to be fast & accurate.
> Having used Bloomberg for nearly 10 years, not only for the front-end but the back-end API
Maybe you know the answer to a question I’ve been asking for years: is there any way to authenticate the data you receive over the API? Bloomberg requires credentials to prove you have a subscription but I’ve long wondered about the security/integrity of the data flowing the other direction. What mechanism stops a bad actor from slightly altering or delaying Bloomberg API data as a way to manipulate the markets?
Once you have a few terminals at your firm, Bloomberg will provide a dedicated router + tunnel on top off the regular security. The bad actor would likely need to be internal to Bloomberg, and at that point there is nothing you can do.
I'm assuming you are speaking about BBDL (Bloomberg Data License). My assumption was the API client used SSL and certificate verification to prevent man-in-the-middle attacks. I'll admit I never verified this. I imagine this is easy to verify -- just do a connect w/ a 2-liner BBDL client script and examine the network.
Adding my data point: as a user of the terminal since 2005 I don't ever remember it crashing. Regarding the API (.Net) the only trouble I've had was when I was using a BlockingCollection to keep my simultaneous requests under the Desktop API limit of 128 and I still received a "too many requests" error -- but I trust Bloomberg's throttling software more than my own so I didn't complain.
Ok your comment is mindboggling to me. Having used Bloomberg for nearly 10 years, not only for the front-end but the back-end API I can tell you it is the most stable piece of software I've ever seen. Not once, not one single time has it crashed in those 10+ years for us. The API is even more impressive- to my knowledge we never even experience a single missed query or randomly dead data stream over all those years.
The terminal is expensive as hell, but they deliver on the cost.
Also just by the fact of how it's used, saying it constantly crashes and assuming it's just like that and traders are ok with that all day long? Whatever experience you seem to have must be an extreme outlier.
>It’s basically a giant piece of legacy code.
Eh I think that's silly. You even say it's designed for the power users, which is absolutly right. That's the only reason you think it's legacy. Are you telling me everything behind and their back-end is not extremely advanced? It has to be to support the amount of data that is flowing through them at every second in data that HAS to be fast & accurate.