Skip to content
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.

Logging #73

Closed
jvirtanen opened this issue Oct 23, 2016 · 4 comments
Closed

Logging #73

jvirtanen opened this issue Oct 23, 2016 · 4 comments

Comments

@jvirtanen
Copy link
Member

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.

@jheusser
Copy link

Btw also worth thinking whether the Aeron-style logging approach makes sense for Parity https://github.com/real-logic/Aeron/wiki/Monitoring-and-Debugging#debug-logging

@jvirtanen
Copy link
Member Author

@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.

@jheusser
Copy link

Cool. Aeron+SBE could probably carry parity-net very nicely (see https://github.com/tmontgomery/Amaethon/).

@jvirtanen
Copy link
Member Author

jvirtanen commented Oct 27, 2016

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

2 participants