refactor SV - connect mbt
A Coggle Diagram about Features todo
(Advanced Orders : Price triggered
, Paper trading/demo
, Jitney (whitelabelling)
, all OS api
and Extra ordertype
, (duplicate orders ?
), deployment - needs to change
, Polling is bad
, need a lot of prelimiry research
and limited by Frontend
), Tech todo
, load test/ stabilize recovery Nexa FIX
, Need Streaming - order updates
, Add FIX session to TK side # #
and ), Pros of moving to MBT
, not inline of the database
, high performance
, existing relational database
and Team is really on a roll
(TK customers cannot use mbt system
, keep running mbt systems ?
, Can't give a timeline on this yet
, if we own it all - what would the end result look like
and What is the Goal / Vision ?
(no SME in house
, how can we make updates as need to the project ?
, as we add new features - add new rest commands, new spring ?
and goes through PHP server
), How to connect MBT ?
(new Connector (takes same input as FL)
, break out- TK users first
and modify desktop Pro ?
(Does SV - have problems right now with Hammering orders? multiple orders coming in
and How does SV provide for diaster recovery - /failover / recovery site ?
), replace TS - phase 2 ?
, Sidewalk updates needed either way
, R &R
), business logic updates