← Back to Trade Talk Blog
For X_TRADER® users wanting to develop their own bespoke trading applications, TT API has long been a solution for applications deployed both client-side and server-side. With the sunsetting of X_TRADER well underway, TT API users need to migrate their applications to the TT platform. TT .NET SDK offers these users a similar solution and an easy migration path, with substantial improvements over TT API.
Continue Reading →Tags: APIs
In my last post, I described the FIX solution provided by TT as “FIX-as-a-service” (FaaS). Indeed, one of the differentiators of TT is that it is a suite of professional trading services delivered using the software-as-a-service (SaaS) model: services that are available from anywhere, on demand, without the need for any pre-allocation of infrastructure or deployment of software.
This is what makes our FIX offering compelling (along with the performance improvements we’ve made along the way), but FaaS is a launching point for two other services that separate TT from the typical “off-the-shelf” trading system: market access and compliance/data-retention.
Continue Reading →
Tags: APIs, Trade Execution
Apama is a streaming analytics service operated by Software AG and a Trading Technologies partner since 2007. Founded in the late 1990s at Cambridge University, Apama was built on complex event processing (CEP) technology, which enables the trading community to execute low-latency trading strategies from the analysis of multiple, disparate streaming data sources.
Today, Apama has built a global client base of over 100 firms, including banks, brokers, prop groups and exchanges across all asset classes. Apama’s algorithmic trading, market surveillance and automated strategies, which are triggered by coded news announcements, leverage Trading Technologies’ connectivity and trading functionality.
Tony Foreman of ApamaI recently sat down with Apama’s Tony Foreman to hear more about the company’s data analysis and how Apama’s services are benefitting TT customers, particularly with regard to recent regulatory changes.
Continue Reading →
Tags: APIs
I was amused by the recent flurry of media releases proclaiming the adoption of algorithmic trading in derivatives markets. Pay no attention to the man behind the curtain, could this be important new information that somehow leads us to enlightened trading? Or is it the case there is nothing more deceptive than an obvious fact? The latter are the words of one well-known sleuth, whose Watson would likely retort, “No kidding, Sherlock,” or something roughly comparable.
|
The infamous Sherlock Holmes |
Avoiding the temptation to offer my own breaking insights, such as The Internet is here to stay! and Mobile communications expected to take off!, I will instead stay the high road, eschewing mirthful gratification for the sake of propriety. As our sleuth would advise, if you eliminate all other factors, the one which remains must be the truth: while other vendors are merely talking about algo trading in derivatives, Trading Technologies has been delivering for several years. I am therefore tickled pink that other vendors are now “discovering” this space. The algos are not missing, they are here. In production. Today.
One of TT’s first algorithmic solutions was our hosted Autospreader® Strategy Engine (SE), which is a very-low-latency computational server for executing synthetic spread algorithms such as calendar rolls, synthetic strips, butterflies and condors. Recent enhancements to this system include intuitive rule building for customized handling of pre- and post-trade hedging, as well as conditional participation and synthetic sniper spreads.
The Autospreader SE product is complemented by TT’s Synthetic Strategy Engine, another proximity-hosted server that provides a suite of algorithmic order types, including synthetic icebergs, TWAP, POV and triggered algos such as stops and if-touched orders.
Continue Reading →
Tags: Algos & Spread Trading, APIs, Trade Execution
The wonders of modern technology are miraculous. Who wasn’t amazed by the news of Voyager I’s departure from the solar system into interstellar space? This feat seems incredible with current technology, let alone with propulsion, guidance and communication systems designed and built almost 40 years ago. With the scientific and engineering capabilities of the modern world, what technology problem can no longer be solved through the concerted efforts of smart engineers?
Let me offer one: financial systems interoperability. “Blasphemy,” you say, “have you not heard of FIX protocol, that cure for the financial industry’s tower of babel?” Sure, I know about FIX (Financial Information eXchange), which includes version 5.0, introduced around seven years ago, as well as the versions firms actually use, namely FIX 4.2 and FIX 4.4, which are 13 and 10 years old respectively.
So what’s the problem with FIX? Before discussing it, I want to clearly state that FIX goes a long way toward enabling integration of financial systems. But it doesn’t go all the way. In a world where fancy toys and even some kitchen gadgets offer plug-and-play interoperability with the Internet, it seems ironic to me that systems used by multi-billion dollar banks and asset managers can take weeks or months to integrate using FIX. FIX gets you into the ballpark, but you have to expend a huge amount of time and effort to locate your seat.
Ambiguity is a major issue, resulting in applications such as back-office and order management systems using different ways of expressing the same thing. You might know that FIX messages are built around sets of tags, where each tag is used to define a required or optional message attribute. The problem is that a fair amount of latitude is granted in the interpretation and use of many critical FIX tags. So the process of integrating two “standard” FIX-enabled systems often involves clunky gymnastics, such as tag remapping, suppression and injection. And no FIX integration effort is complete without the conformance test process, which often involves a fair amount of trial and error to get things right. This requires a lot of time and money, and can result in brittle integrations that often don’t accommodate new financial instruments without additional work.
Continue Reading →
Tags: APIs