3 ms·
I can only imagine some investment banks have donated a fair bit given that HAProxy now has built in support for FIX. I really wasn't expecting to see that!
by osrec 5y ago
I can only imagine some investment banks have donated a fair bit given that HAProxy now has built in support for FIX. I really wasn't expecting to see that!
- deleted 5y ago[deleted]
- oogali 5y agoSince ~2004, folks in the financial industry have been migrating away from FIX to other lighter protocols such as ITCH, OUCH, and SBE (standardized from FAST: "FIX Adapted for Streaming"). This is analogous to the move we're all witnessing from HTTP to HTTP/2 (standardized from SPDY) and HTTP/3 (QUIC). The desire to reduce the amount of bandwidth spent pushing uncompressed text around and reduce the amount of CPU needed to parse strings is what spurred market participants to explore alternatives to FIX, namely in the form of binary encoded message that costs less to parse (from a CPU and bandwidth perspective). As libraries release support for alternative protocols and the industry compiles their projects against these newer versions, the adoption of non-FIX will keep increasing. Similar to how you get HTTP/2 for "free" when using the Go stdlib so its downstream consumers such as Caddy and Traefik can provide that as a default to end users. https://en.wikipedia.org/wiki/List_of_electronic_trading_protocols https://en.wikipedia.org/wiki/List_of_electronic_trading_pro... EDIT: Added year for context on timeframe of first implementations