We use cookies on our website to personalise your experience, you may accept or decline the use of cookies.. Learn More or Accept

Case Study

HEDGD FIX

Key Tech

Highlights

Details

Seeking to eliminate manual execution and dual entry one of our clients approached us about bringing forward our plans for FIX connectivity. We were happy to oblige and built a FIX micro service using the QuickFIXn library with service bus providing the communication channel between our OMS and the new micro service. Connectivity was via the FIDESSA network.

We like to measure twice, cut once, so we built a small FIX simulator to put our client through its paces. The simulator included a generic action class which made it trivial to add new test scenarios as we needed them.

// Reject then accept client initiated cancel request
var scenario = new[]
{
    ServerAction.AcceptNew,
    ServerAction.PartFill,
    ServerAction.AwaitCancel,
    ServerAction.PendingCancel,
    ServerAction.RejectCancel,
    ServerAction.PartFill,
    ServerAction.AwaitCancel,
    ServerAction.PendingCancel,
    ServerAction.AcceptCancel
};
Configuring a scenario for the FIX simulator

On the client side the new service allowed us to provide mobile FIX connectivity, and also gave us an opportunity to augment the app with features like FIX status indicators and a built in FIX message viewer.

No FIX service is complete without monitoring and admin tools so we implemented various health checks, a status page, and alerts delivered via email plus slack. An admin dashboard allowed failed messages to be discarded or replayed, rounding out the offering.