How Open Source Trading Systems Improve Profitability

As a trader, you know how thin margins have been stretched. You have to be even smarter, even faster, and even more disciplined to grind out a profit in the world of high frequency trading.

A few seconds can mean the difference between a profit and a loss, so traders need agile, nimble systems that can respond to the complexity and speed of today’s markets.

If a malfunction occurs, it needs to be identified and resolved immediately, preferably by your own support desk or development team, if not by the software vendor. Either way you should have the ability to access the source code of your trading platform to troubleshoot the software to solve issues right away.

Unfortunately, one of the major problems with the current state of trading software is that it is built on the old, brittle, closed proprietary model.

In this article, we’ll take a look at how closed trading systems fail you and how you could save money by making the switch to open source software.

What is closed system proprietary software?

If you are currently using trading software, chances are it’s a closed system – in other words the source code is not available to the public.

That essentially means that the only people who can detect or fix problems in the software are employees of the provider, or their outsourced customer service team.

So when something goes wrong like a bug or a defect in the code, the software provider is the only one who can fix it.

We’ll talk about why that’s a problem later in this article when we discuss the benefits of Open Source Software.

When closed systems fail:

The pattern with closed-source software is usually that a defect report will be filed and then there will be a delay as the vendor decides whether or not to issue an update.

Because the system is closed, you have no access to the source code to determine the cause of the problem or make a fix yourself. You lose control of the situation as the vendor determines the timing of next steps.

This delay can cost a fortune in missed opportunities as the software vendor’s team considers when to fix the defect.

Open Source Software:

Open source software offers a different model.

OSS is a software development methodology defined by human readable code made available in the public domain and a spirit of community and collaboration.

When software is open source, the code is available to the public and developers or authors are free to search for bugs, suggest improvements and contribute to the evolution of the software.

How OSS fixes bugs

One of the great strengths of OSS is its reliability or it’s ability to avoid bugs.

We’ll define bugs as defects, which cause incorrect operation, data loss, or sudden failures of the software.

In fact OSS offers a much faster time to fix than closed systems. Because of the availability of the source code, severe defects tend to be fixed within hours of being detected. Authors who discover a bug will commonly fix it and then report it to the maintainers as well as issuing their own update. Users then have the choice of either using the unofficial fix or waiting for an “official” version.

OSS encourages a large market of early adopters who actively help to debug the software leading to a high level of robustness in open source products.


In computer science the term robustness refers to the ability of a system or software to cope with errors during execution.

Robustness means that software has gone through the necessary troubleshooting it needed and is now ready to function without any bugs defects or problems that can cost you millions of dollars in the blink of an eye. In other words it is reliable.

Because of the network of authors and developers OSS becomes robust much earlier than closed systems do because developers enjoy debugging the code and can gain status and legitimacy for their work. These incentives lead to more debugging and a better overall product for the consumer.

I started this article by having you imagine your trading software malfunctioning, the system crashing and you losing out on the trade of a lifetime.

Bugs and software malfunctions are a part of life in the digital world, but you don’t have to become a hostage to delayed responses from software vendors or updates that take weeks to arrive.

Make the change to Open Source trading software today by downloading Marketcetera Here and joining the Open Source Software Movement!

How Trading Has Changed, and Why That’s Bad For Proprietary Trading Systems.

Trading, whether it’s stocks, bonds, forex, or any other kind of asset class has changed dramatically over the last few years. Technology, the financial crisis, and new regulations among other factors have combined to make trading in 2016 and beyond look completely different than what has come before.

This is bad news for the old ways of doing business and even worse news for the closed systems that were previously used in trading.

How Trading Changed

Since the financial crisis we have seen the emergence of “high frequency trading” (or what we simply call today “trading.”) High frequency trading (HFT) uses high-speed computers and software to enter and exit trades based on algorithms related to price, volume and other variables.

The rise of HFT has been exploited by bad actors introducing techniques such as quote stuffing in order to gain an unfair edge.

At the same time as HFT was becoming the new normal, government regulators are becoming more determined to crack down on the bad actors and are issuing more and more regulations leading to a need for greater transparency both for the government and for investor peace of mind.

Meanwhile, the trading community now has to keep up with the new latency norms, avoid the actions of bad actors and comply with all the new regulations!

Compounding these problems is the old model of brittle, closed, proprietary software.

The Weaknesses of Closed Systems

One of the major problems facing trading firms is the historic industry reliance on closed trading systems.

These systems are sold and maintained by service providers who are already focused on their next sale by the time you’re setting up your system.

Proprietary service providers are waging a territorial battle for your company’s IT budget. Once they establish a beachhead, they want to upsell you with ancillary services and technologies. Start with market data and expand with a trading platform. Start with a trading platform and offer custom algorithms. There is no incentive in this model to make their technologies open or extensible or to make it easy to integrate with other technology solutions you have implemented in your environment. They certainly do not want to make it easy for your team to do your own integration work.

Furthermore, because the systems are closed, meaning that their source code is not openly available, bugs and glitches which could cost you hundreds of thousands of dollars in a single trade have to be fixed by the supplying company.

If they even notice them…

As I mentioned earlier their focus is on selling the same software to the next customer rather than making sure it’s bug-free.

What is Open Source Software?

The alternative to closed trading systems is open source software or OSS.

Founded in the 1970s out of the Free Software movement, which sought to combat soaring software prices, the basics of the open source philosophy are that better software is created through transparency of code and widely distributed peer review.

This leads to high quality software and documentation without the expensive licensing fees.

One of the most common misconceptions about OSS that has kept it from becoming more popular in the trading community is that you will have to reveal your proprietary algorithms or other trade secrets.

Nothing could be further from the truth!

You can download and use OSS software without ever revealing how the software is being used!

Because there are no sales people or license compliance checks, you could argue that OSS is actually safer than other commercial systems on the market because there are less people involved in the process.

Let’s look at 3 more benefits of using OSS:

1. Flexibility. Software flexibility is all about being able to choose solutions suitable for the end user which is you. This means that the software should be built with a flexible infrastructure, which will allow the trader to be agile and pivot when necessary to change strategies or cash in on new trends. OSS is the most flexible because there are no financial incentives to lock down one system or make it proprietary.
2. Freedom. Another major benefit to OSS for trading is freedom. Freedom from your software vendor. No longer will you be at the whims of some software developer you’ve never heard of or a company that might go out of business one day. In addition to freedom from software suppliers, you can also gain the freedom to modify your software however you see fit. You are no longer limited by what a company believes you need. Your software can be completely tailored to your trading business.
3. Cost. Closed trading systems can cost hundreds of thousands of dollars, whereas most OSS trading systems such as Marketcetera have free downloads like you can find Here. Additionally, if you do need a commercial license for a commercial module to accelerate your deployment or technical support, these services are also available.

In this article we looked at how trading has changed, and why that is bad news for closed systems.

We started off by taking a look at how trading has changed specifically looking into how high frequency trading has made life more complicated for today’s traders.

Then we examined why these new developments are bad for closed systems, most notably the lack of transparency and the focus on marketing more software rather than making sure the software is meeting the user’s needs.

Lastly we looked at what Open Source Software is, essentially free to download software that is fully customizable and supported by a community of developers and authors who find and fix bugs before they become problems, and consistently revise the software so it becomes better.

The benefits of OSS are increased flexibility, freedom to design the software however you want and a way way lower cost.

By now the choice is clear, closed systems are going the way of the dinosaur and OSS trading systems are the way of the future.

Download your FREE copy of Marketcetera Here.

The Future of Trading – Both Faster and Smarter

These days, high-frequency trading (HFT) is a controversial topic in economic discussions. Critics bemoan the proliferation of high-speed trading. They claim it destabilizes global financial systems, while proponents say that HFT is a natural progression in the development of new financial-trading tools.

As algorithmic trading continues to advance, the line between human trading and machine trading is becoming blurred. It’s difficult to guess the upper limits for speed in trading. Yet, the next wave of evolution in technology for trading is likely to be the expanded use of artificial intelligence (AI) to build trading systems which trade smarter instead of merely faster. Continue reading

Evolving Toward Simplicity

The HFT pursuit has triggered a technology arms race across our industry with tremendous capital (human and financial) expended chasing elusive microseconds.

In the midst of this full-throttle pursuit, it is worth considering some of the fundamental assumptions of great software design. One of the most basic (and often over-looked) questions is whether to pursue a proprietary system or opt for an open source approach.

Continue reading

Spring is in the Air

It’s finally spring and with the “extra hour” courtesy of the DST change you might think the entire Marketcetera team would be out “spring-snowboarding” at Squaw in Tahoe. Well, the snow is slushy, so let’s talk about “the other” Spring instead. Since version 0.2, we are using the Spring Framework to do IoC-based configuration of our server-side components, and we love it. Many transformations of our code become almost trivial when using Spring. As an example, we have recently been working on supporting all versions of the FIX Protocol in our OMS. Until now the OMS only supported FIX.4.2. While that is likely the most common dialect of the protocol, we needed to be able to choose a version of FIX at deploy-time.

Continue reading

Java and the Computer Language Shootout

The Java VM is an impressive beast. In theory, features like dynamic optimization and compilation and concurrent garbage collection promise great performance gains. But in benchmarks at the Computer Language Shootout, performance numbers still appear to be lacking.

The Computer Language Shootout is good research. Complete disclosure of methods (for maximum reproducibility), an adversarial method for developing implementations and the breadth of language and compiler coverage all make for a solid data set. However I began to wonder about the fact that for each benchmark results are only published for one set of inputs. Update: As Isaac Gouy points out, there are actually three results reported, see comments below. For example for the binarytree benchmark, only one tree-depth is used, specifically 16. This value may be an arbitrary choice, it may be chosen to keep the runtimes in some range, regardless, there is only one.

Continue reading