Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unify EMS messaging set #514

Open
3 tasks
goodboy opened this issue May 24, 2023 · 0 comments
Open
3 tasks

Unify EMS messaging set #514

goodboy opened this issue May 24, 2023 · 0 comments
Labels
accounting prolly positioning: the accounting of "what/when (is) owned" clearing auction and mm tech: EMS, OMS, algo-trading factoring less codez dawg

Comments

@goodboy
Copy link
Contributor

goodboy commented May 24, 2023

More or less the idea would be to drop the BrokerdX side messages from
.clearing._messages with the intention of:

  • allowing the order client to work seemlessly by connecting to the
    emsd or directly to the .brokers.<backend>.broker of choice.
  • minimizes complexity in general and would make testing a single
    dialog "side"/leg of emsd much simpler (particularly if we end up
    needing to mock some services)
  • allows us to drop BrokerdPosition and instead unify it with
    .accounting._pos.Position

.. more to come

@goodboy goodboy added factoring less codez dawg clearing auction and mm tech: EMS, OMS, algo-trading accounting prolly positioning: the accounting of "what/when (is) owned" labels May 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accounting prolly positioning: the accounting of "what/when (is) owned" clearing auction and mm tech: EMS, OMS, algo-trading factoring less codez dawg
Projects
None yet
Development

No branches or pull requests

1 participant