Episode 5: Establishing a Voice Trading Engine for a Distributed Ecosystem

As the financial industry continues to transition towards a predominantly virtual environment, institutional traders need to be able to easily access the right tools to stay connected and enhance workflow efficiencies. In the fifth episode of Cloud9’s podcast series examining developments in the voice trading landscape, Cloud9’s Chief Innovation Officer and Co-founder Leo Papadopoulos, and Chief Operating Officer Jim Miller, examine what voice trading capabilities institutional traders must have in a distributed workplace and how a cloud-based platform can provide a more secure, mobile and accessible ecosystem.

You may also like

Tech4Fin

A Communication Transformation: Broader Access to Voice

More than ever before, business success depends upon an organization’s ability to communicate quickly and effectively. It’s clear that the “workplace” has radically changed. This new landscape demands three things from every company’s communication tools:

Tech4Fin

Accelerating transaction settlement demands a fresh approach to communication

In December of 2021, SIFMA, ICI and DTCC called for the shortening of the settlement cycle in the U.S. financial markets from T+2 (transaction date plus two days) to T+1 (transaction date plus one day) within the first half of 2024. Their report indicates that accelerating the settlement process will “reduce risks and costs for the industry while building upon the benefits achieved in the successful move to T+2 in 2017.” This is in line with the Securities and Exchange Commission’s announcement on Feb 9, 2022 of a proposed rule to shorten the standard settlement cycle for most broker-dealer transactions from two business days after the trade date (“T+2″) to one business day after the trade date (“T+1″), while soliciting comments regarding challenges and possible approaches to achieving settlement by the end of trade date (“T+0″).

Tech4Fin

Carrying over history to the mesh

In our journey building an event mesh, we face the challenge of reconciling with Symphony’s engineering history. Specifically, we are transitioning from a single-tenant, monolithic architecture to a multi-tenant, microservice architecture. And critically, due to the nature of our business, this shift must be both progressive and smooth.