Industry


Ads by TechWords

See your link here


London Stock Exchange to abandon failed Windows platform

Anyone who was ever fool enough to believe that Microsoft software was good enough to be used for a mission-critical operation had their face slapped this September when the LSE (London Stock Exchange)'s Windows-based TradElect system brought the market to a standstill for almost an entire day. While the LSE denied that the collapse was TradElect's fault, they also refused to explain what the problem really wa. Sources at the LSE tell me to this day that the problem was with TradElect.

Since then, the CEO that brought TradElect to the LSE, Clara Furse, has left without saying why she was leaving. Sources in the City-London's equivalent of New York City's Wall Street--tell me that TradElect's failure was the final straw for her tenure. The new CEO, Xavier Rolet, is reported to have immediately decided to put an end to TradElect.

TradElect runs on HP ProLiant servers running, in turn, Windows Server 2003. The TradElect software itself is a custom blend of C# and .NET programs, which was created by Microsoft and Accenture, the global consulting firm. On the back-end, it relied on Microsoft SQL Server 2000. Its goal was to maintain sub-ten millisecond response times, real-time system speeds, for stock trades.

It never, ever came close to achieving these performance goals. Worse still, the LSE's competition, such as its main rival Chi-X with its MarketPrizm trading platform software, was able to deliver that level of performance and in general it was running rings about TradElect. Three guesses what MarketPrizm runs on and the first two don't count. The answer is Linux.

It's not often that you see a major company dump its infrastructure software the way the LSE is about to do. But, then, it's not often you see enterprise software fail quite so badly and publicly as was the case with the LSE. I can only wonder how many other Windows enterprise software failures are kept hidden away within IT departments by companies unwilling to reveal just how foolish their decisions to rely on archaic, cranky Windows software solutions have proven to be.

I'm sure the LSE management couldn't tell Linux from Windows without a techie at hand. They can tell, however, when their business comes to a complete stop in front of the entire world. 

So, might I suggest to the LSE that they consider Linux as the foundation for their next stock software infrastructure? After all, besides working well for Chi-X, Linux seems to be doing quite nicely for the CME (Chicago Mercantile Exchange), the NYSE (New York Stock Exchange), etc., etc.

What People Are Saying

The truth is like the sun

You cannot hide it with your hand.

Costs

The issue seems to be costs, rather than performance. Either way, GNU/Linux is a better performing/lower-cost platform.

It must take quite a bit of time and energy to decide to switch and to make the switch so I doubt the change is imminent. It will be interesting to see what software they run on the servers on top of GNU/Linux.

I have not seen any application perform as well on that other OS as on GNU/Linux. Some report that one-third as many servers are required to do the same job with GNU/Linux. Will LSE turn the surplus servers off? We shall see. They are looking at shedding staff soon so that is consistent with a quick changeover. Perhaps a deal has already been done.

Hardware and software license cost insignificant

When are Linux proponents going to realise that harping on about free licenses and cheaper hardware is pointless? In the average enterprise IT project, these costs form only a tiny proportion of the deployment and support costs.

When you factor in the use of RHEL (most enterprise's chosen Linux platform), then the software support license costs don't really bring a financial advantage over Windows servers.

The only thing that matters is the business capability of the deployed systems - it makes absolutely zero difference to the business whether they run Red Hat, Solaris or Windows 98, as long as the capability is there and reliable at the lowest cost. If its cheaper and just as reliable to push out a pool of 20 Win2k3 servers than a pair of Solaris boxes, then why choose Solaris or *nix?

I think you answered your own question...

"If its cheaper and just as reliable to push out a pool of 20 Win2k3 servers than a pair of Solaris boxes, then why choose Solaris or *nix?"

Well, because it isn't cheaper, and it SURE as heck isn't as reliable.

When you go Windows, not only do you have your server and desktop licenses, but you have your client access licenses for every device connecting to the server itself, for Exchange, and for SQL server, etc... and then you've got to have licenses for your antivirus on all those machines, and software assurance if you don't want to get screwed on the upgrade, and you have to have more machines to do the same work, and these machines have to be more powerful because Windows is a resource hog, so you spend more on electricity and cooling.... jeez, the costs just keep adding up! And then you call for support, and you get charged a ridiculous rate. Oh, and then you need to pay $300 a machine for MS Office licenses. So there goes your cost argument...

And I don't think I even have to start on the reliability argument -- if you think Windows is even AS reliable as a *nix, you're a step away from a home for the mentally disturbed.

Not exactly

The Exchange is run on many 2003 servers, but there is most definitely a volume license for both the servers and the SQL instances. Also since a mission-critical environment is needed there is more than likely no antivirus software required. These servers I'm sure were very finely tuned with respect to resources, etc. It's not very difficult to get a very fast stable/reliable 2003/2008 server running very few services – turning on only what is needed.

_ _ _

And I don't think I even have to start on the reliability argument -- if you think Windows is even AS reliable as a *nix, you're a step away from a home for the mentally disturbed.
_ _ _

And if you really think that, you are incredibly ignorant.

Are you sure you want the LSE to try Linux though?

If the LSE management was stupid enough to botch the existing installation as badly as they did, they are perfectly capable of botching a Linux or UNIX installation as well.

While Windows may have been the wrong platform, the fact that management went with it, stuck with it, and eventually failed with it indicates a perfect capacity to screw up anything they touch. Kind of like the Midas Touch in reverse.

Sticking with a costly decision

It is difficult to abandon a software system after it is implemented. It must be a 'massive fail' in order to acknowledge that is it crap and remove it. I've been in situations where the software chosen has been utter crap, yet we are expected to make it work. After months or years of problems, only then will the decision makers re-visit the question, to keep or purge.
GNU/Linux is the path to productivity.

LSE management was stupid

From TFA:
"...the CEO that brought TradElect to the LSE, Clara Furse, has left without saying why she was leaving..."

So they are getting a platform change and a management change. From my experience there are several Microsoft shops that will require this type of intervention before they can break the amazingly expensive cost of running Microsoft sub par software products.

CEO v.s. CTO

Thats right the CEO left not the CTO. The CEO made a bad spending decision with regards to the technology they used.
The CTO was the one that probably proposed to use the M$ crap in the first place.
This still means that LSE could still F&*% up even with Linux as their platform.

This was a management call

The LSE outsourced the whole thing from soup to nuts to MS and Accenture.

LSE's in-house IT was Not amused.

I strongly suspect that this was one of those sweetheart deals where the customer pays less and MS got to trumpet how the project showed how enterprise-ready the MS software stack was.

Except, of course, as events have shown, it was anything but enterprise ready.

Frankly, the project appears to have been mismanaged from moment one. While I certainly would never have built anything like this on top of MS software, they could have made it faster and more stable just using other MS programs. I mean SQL 2000!? SQL Server 2003 was already out and battle-tested by the time this project was under way.

While I like to kick MS around when they blow it, the integrators on this one probably should take the lion's share of the blame.

Steven