The December 2022 issue of IEEE Spectrum is here!

Close bar

A few weeks ago, I blogged about the new London Stock Exchange (LSE) trading platform, Turquoise, that had achieved a world record trading time of 126 microseconds in tests. The new platform is intended to replace the LSE's Tradelect system.

Yesterday morning at 0823 London time, however, Turquoise suffered a problem that required it to be shut down until 1030. According to a statement by the LSE, the shutdown was due to "human error [that] may have occurred in suspicious circumstances."

The London Guardian put it a bit more plainly: possible sabotage by parties unknown.

The police have now been called in to investigate. This is now the third "glitch" the LSE has had in trying to roll out its new platform.

The LSE went on to say in its statement that:

"In light of this incident, coupled with necessary network upgrades to address ultra low latency and high flow inherent in the new platform, the Group has regrettably been forced to postpone its Main Market LSE technology migration for SETS [Stock Exchange Electronic Trading Service]. Given that December is an agreed change freeze period, the London Stock Exchange Group will work in partnership with customers to agree a date as early and practicably as possible in 2011 to reschedule the Main Market migration."

This is developing into an interesting story that I will continue to follow in the weeks and months ahead.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}