A fast, low-latency Financial Information Exchange (FIX) protocol library for the JVM.
Philadelphia is a Financial Information Exchange (FIX) protocol library for the JVM, designed to facilitate fast and reliable communication with financial systems like stock exchanges and brokerage firms. It implements the FIX protocol standards, enabling developers to build trading applications, market data feeds, and order execution systems. The library focuses on minimizing latency and memory overhead to support high-frequency and algorithmic trading environments.
Java developers building trading platforms, financial middleware, or connectivity solutions for exchanges and brokers. It is also suitable for quantitative analysts and firms requiring low-latency FIX protocol integration.
Developers choose Philadelphia for its emphasis on performance, with features like non-blocking I/O and zero memory allocation during message handling, ensuring predictable latency. As an open-source library, it provides a cost-effective, customizable alternative to commercial FIX engines, with support for multiple FIX versions and a modular design.
Fast FIX protocol library for the JVM
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements non-blocking networking and zero memory allocation on message handling, as per the README, ensuring predictable performance crucial for high-frequency trading.
Includes separate libraries for FIX 4.0 through 5.0 SP2 and FIXT 1.1, covering a wide range of protocol standards used in financial exchanges.
Separates core protocol logic from version-specific profiles and provides a code generator for custom FIX dialects, facilitating easy customization and maintenance.
Released under Apache License 2.0 with active community discussions on GitHub, offering a cost-effective, transparent alternative to proprietary solutions.
Requires JRE 11 or newer, which may hinder adoption in legacy systems or environments with strict version constraints, as noted in the README.
Focus on performance means developers must handle low-level networking and message parsing directly, increasing boilerplate code compared to more abstracted FIX engines.
As a library, it lacks integrated monitoring, logging, or GUI tools, requiring additional development effort for administrative features beyond core protocol handling.