FerrumFIX is a free and open source FIX engine implementation in Rust. Please note that it’s currently under heavy development and wildly unstable, so all interested parties should refrain from using it in production prior to its 1.0 release. Performance and full adherence to the FIX protocol are nevertheless core goals of the project which, if anything, might serve as a useful foundation for others’ work.
FerrumFIX provides parsing, validation, error recovery, and (de)serialization for the FIX family of protocols.
The above illustration succintly describes the full scope of FIX and it serves as a reference point for all modern FIX implementations. FerrumFIX aims with total compliance… eventually. Engineering efforts are initially focused on core features e.g. tag-value encoding and FIX 4.4.
FerrumFIX enforces strict separation of concerns according to the OSI model, as reasonably allowed by the FIX specification.
- Layer 4 (Transport Layer):
- Layer 5 (Session Layer):
- Layer 6 (Presentation Layer):
- Layer 7 (Application Layer):
You don’t have to understand the whole tech stack to use a single layer; in fact, FerrumFIX makes sure that you only ever need to worry about layers above your chosen abstraction level. For most users, that would be Layer 7 (i.e. semantics of FIX messages and business logic). On the other hand, you will need to delve deep into lower layers in case you plan on building a fully-fledged FIX engine.
- Code generation (Rust, possibly others).
- FIX 4.2.
- FIX 4.4.
- FIX 5.0 Service Pack 2.
- Tagvalue (classic FIX).
- Simple Binary Encoding (SBE).
- Google Protocol Buffers (GPB).
- Abstract Syntax Notation (ASN.1).
- FIX Adapted for STreaming (FAST).
FerrumFIX is kindly sponsored by Bitwyre. Bitwyre is a next gen, HFT-friendly Cryptocurrency Derivatives Exchange.
Please reach out to
Filippo Costa <firstname.lastname@example.org> for business inquiries.
All development happens on GitHub at
neysofu/ferrum-fix. Contributions both from volunteers and companies are welcome. Depending on the size and scope of your intented contributions, it’s likely a good idea to open beforehand a GitHub issue to discuss any details. Please note that our branching strategy is inspired by the (in)famous Git Flow, which is a good fit for software that requires complex versioning such as FIX implementations. Versioning adheres to SemVer 2.0.
FerrumFIX is available under the terms of the MIT license and Apache License 2.0, at your choice. See
LICENSE-APACHE.txt in this repository for more information.
All FIX Protocol-related intellectual property, including but not limited to the original documentation that ships with FerrumFIX, is licensed by FIX Protocol Ltd. under Creative Commons Attribution - No Derivatives 4.0 International (CC BY-ND 4.0). By contributing to this project you agree to comply with all license requirements.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.