High availability is a constant and critical requirement in today's highly volatile trading environments, which is why our components have native features enabling firms to use the same architecture and processes regardless of the number of servers in place.

FailOver

Each process running our components may be deployed using a primary / secondary model where the state of the primary server is replicated to the secondary in real-time. It ensures an immediate uptime in case of failure of one of the servers. In parallel, all state changes are recorded in transaction logs offering a way to restate the components in case of cold restart. Several deployments scheme are available in order to support the high availability constraints of our clients.

Scalability

A pair of primary / secondary server is called a Partition. The overall traffic may be dispatched to specific partitions following dynamic routing rules. This repartition may be managed differently depending on the type of component and the client deployment. STConnect, our client API, has been designed to fully support the failover model and manages transparently the overall repartition of the process across the infrastructure.