Move to a websocket, message bus and event driven architecture

[sebastienverreault]

The current dealer is kicked off and runs as a background (cron) job, actively gather's data (handles errors, etc.) and results in actions to trade or transfer funds. An event driven real-time version of that would most likely simplify and make the code more straight forward. Data, or the best available version of it, would be readily available. Calculations, decisions and other actions would then cascade from the real-time changes in data becoming more data for downstream. Business logic would be encapsulated in read conditions in, output decisions/actions out to sinks dedicated to executes those actions. So a snapshot of the message bus at any point in time represents the best information available at that point and the actions to be taken. Factoring in the propagation delays thru the feedback loop, the dealer becomes a more dynamic and globally observable system chasing its steady state.