Thomson Reuters internal cloud strategy expands


Thomson Reuters internal cloud strategy expands

Karl Flinders

Real-time information provider Thomson Reuters' project to create internal clouds to support the increased use of algorithmic trading by its investment firm customers has expanded.

The project, known as Elektron, saw the company initially build seven datacentres across the world to enable its customers to connect to its information. It also offered customers the opportunity to put their systems next to its own systems to speed up the transmission of information.

Every 200km reduction in fibre cuts one millisecond. A millisecond is a relatively long time when trades are being completed on trading venues in microseconds.

Thomson Reuters has now added datacentres in Hong Kong and Mumbai to those in New York, Chicago, Tokyo, Frankfurt, Singapore and London.

The company has developed the core software itself with some of the work completed in Bangkok and Beijing.

Investment firm computers need to be connected to real-time information. Elektron means the information is collected and standardised in a cloud next to the trading venues then fed to the client company via dedicated high bandwidth links. Traditionally the data would travel from the trading venues to hub datacentres in three global locations where all the information is put into a standard format. It would then be sent to the customer.

Mike Powell, global head of Enterprise Information, said demand for Elektron from customers has been good and that the company is looking at building datacentres in more locations.

Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

COMMENTS powered by Disqus  //  Commenting policy