Warning
HotFIX is currently in development with frequent breaking changes to the API and some features missing.
HotFIX is a FIX engine implemented in Rust. While the ambition is to create a robust, fully compliant, ergonomic and performant engine eventually, this is a large undertaking.
The near-term goal of HotFIX is to provide a functional and useful engine for the buy-side (initiators), reaching full support of FIX 4.4 and 5.0 workflows as soon as possible.
- Network layer including TCP transport with optional TLS support using
rustls - Message encoding and decoding (FIX 4.4)
- Session-layer supporting the core flows, such as logins, resends, etc.
- Built-in message stores
- Code-generation for FIX fields from XML specifications
- FIX 5.0 support
- Code-generation for complete FIX messages from XML specification
Check out the examples to get started.
The two major influences for HotFIX are QuickFIX and FerrumFIX.
QuickFIX implementations in various languages (such as QuickFIX/J) have influenced the design of the transport and session layers. The FIX message logic builds on QuickFIX XMLs for the specification. People who are familiar with QuickFIX will find the API familiar.
The FIX message implementation of HotFIX is a fork of FerrumFIX for things like codegen, parsing the XML specification, defining fields, etc.
In its current state, the engine has a lot of issues that will be fixed in due course, so please don't create issues or PRs for individual bugs.
We welcome committed contributors who want to work with us to turn this into a successful project. There are many components that can be developed in parallel. If you are interested in participating, don't hesitate to reach out.
The best way to get in touch is by starting a Discussion.