Java apps in Tbricks by Itiviti

By Katarina Klangby, Director Content Marketing
May 16, 2016
Share:

The basic design concept of Tbricks by Itiviti is modular: a high-performance system core is complemented by independent apps that contain all business logic. The apps are ready to use out-of-the-box but can also be customized, often using zero lines of code. However, when coding is required, C++ has been the only option — until Tbricks 2.8, due out in May. For the first time, Tbricks now offers a Java apps API. We asked Tom Williams, Assistant VP Sales Engineering Itiviti to explain.

Tom Williams, C++ or Java — does it really matter?

There are pros and cons with both languages, of course.  A Java fan might say that Java is more user friendly, while the C++ advocate could argue that C++ is faster. But in the end, I think it boils down to personal preference, the firm’s current code base and the right tool for the job.

Why does Itiviti introduce Java apps in Tbricks?

To keep an edge in the constantly changing financial markets, our customers need the power to adapt their systems at any time. Tbricks is Itiviti’s main trading platform going forward, and it was designed for change from the start. All Tbricks’ business logic is delivered as apps combined with a high-performance core. All apps come with development tools and complete source code, allowing you to customize or copy them to use as blueprints for proprietary apps. With the introduction of the Java apps API, the transition to Tbricks is easier if you already have in-house Java competence and a Java code base, as you might if you currently use Orc Liquidator by Itiviti.

Will all Tbricks features be available in both languages?

Yes, there will be complete feature parity between the Java and C++ APIs. Anything you can do in C++, you can also do in Java.

If a firm has no preference, would you recommend Java or C++?

Anything you can do with an app with the C++ API in Tbricks, you will also be able to do with Java, but my advice would be to use both depending on the use case. As a general rule, for anything extremely latency-sensitive you should still use C++.  The core of Tbricks (as with Orc Liquidator) is written in C++, meaning that any code written in Java requires a translation through a middle-layer which adds a little overhead. On the other hand, time to market might be quicker with Java, especially if the developer is used to that language.  

As an example, if you were writing a trading strategy you may use C++ because performance is important, at the cost of potentially taking longer to implement. If you were writing an app that is not latency-sensitive, such as an app to manipulate static data or a risk report, you might use Java to speed up time to market.

It is really less about learning Java or C++, and more about learning how to write an app in Tbricks. If you’re used to one of the languages, you can switch between the two quite comfortably, at least on the level required to create or customize a Tbricks app.  We want people to focus on writing business logic, not boilerplate code. Our core technology takes care of a lot of this anyway so that you can just focus on writing what’s important to you.

What is the single most important advantage of Java-enabling Tbricks apps?

The Java apps API is a new choice for rapid development, empowering firms to leverage their existing Java code base as well as the huge selection of open source, third party and enterprise integration solutions that are available to the Java community.

The Java apps API will be introduced in Tbricks 2.8, due out in May.

Related Content

Systematic Internalisers: opportunities in a post-MiFID II world

Systematic Internalisers: opportunities in a post-MiFID II world

Execution In the months following the implementation of MiFID II, we have seen and will continue to see a number of Systematic Internalisers (SIs) appear on the market – some of their own volition, some following ESMA’s publication of benchmark data and thresholds. What we have seen is that many of these SIs started off by […] September 18, 2018

Why infrastructure testing is critical to your trading business

Why infrastructure testing is critical to your trading business

FIX Infrastructure End-to-end testing of trading infrastructure is critical in today’s increasingly heavily regulated environment – but compliance comes at a price. So why should financial firms pay it, and what happens if they don’t? In our second blog post on the topic, we explore the most pressing reasons to implement a robust testing mechanism. The most […] September 11, 2018

Trading infrastructure testing and why it’s important

Trading infrastructure testing and why it’s important

FIX Infrastructure As trading processes become ever more sophisticated and regulators race to catch up, the end-to-end testing of trading infrastructure is an increasingly crucial component of compliance. Financial services firms face severe penalties for trading errors – including fines, loss of reputation, potential bankruptcy and even personal repercussions for senior executives. The cost of failure is […] August 21, 2018

Multi-asset platforms well equipped for Forex trading as markets converge

Multi-asset platforms well equipped for Forex trading as markets converge

Trading Forex trading is increasingly influenced by and synchronized with equities. With this trend come new opportunities and challenges for Forex market participants. The trading styles and tools traditionally used for Forex are converging with other asset classes, enabling multi-asset and true cross-asset trading, and presenting an opportunity to consolidate and streamline trading technology. Download the […] August 7, 2018

Itiviti Talks

Get our view on global capital markets

Subscribe

Subscription successful

Thank you for subscribing!

Close window

Itiviti Talks

Get our view on global capital markets

Weekly email

    Trends in global capital markets from a technology perspective.

By submitting this form, you acknowledge that data collected by us will be handled in accordance with our Privacy Notice.