You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.
Both Parity Trading System and Parity FIX Gateway should implement logging to help with setting up and debugging. The bare minimum would be to log the configuration at the startup.
The text was updated successfully, but these errors were encountered:
@jheusser Interesting, I have to take a look at that. Also, I have for some time now been considering using Aeron for inter-process communication within the trading system.
SBE looks to be the successor of FAST for FIX market data. I think it would be a possible future alternative to the native market data protocol, PMD, similarly as FIX is an alternative to the native order entry protocol, POE.
For inter-process communication within the trading system I have thought about simply running the native protocols on top of Aeron as they already have simple, fixed binary representations. In case of POE, for example, SoupBinTCP, the underlying transport protocol, would be replaced by Aeron between the FIX gateway and the trading system.
Both Parity Trading System and Parity FIX Gateway should implement logging to help with setting up and debugging. The bare minimum would be to log the configuration at the startup.
The text was updated successfully, but these errors were encountered: