Your team has been asked to write a new Trading application. You work with an Algo team who provide you a library containing all the required Trading Algo software and the job of your platform is to execute the Algo when given a ‘signal’. In the following section the ‘Algo’ class belongs to the Trading Algo library and cannot be modified.
Your team has written the ‘TradingApplication’ code to be able to process one of these signals (a simple integer). Each signal specification is given to your team in the form of a JIRA from your analysts. The role of your team is to implement the new signal specifications and release to production as quickly as possible. While the current ‘TradingApplication’ code only has three signals, once in production it is expected that up to 50 new signals will be added per month (600 after year one, 1200 after year two etc).
We would like you to make any changes to your teams code to make the code: Receive signals via HTTP instead of the SignalHandler interface. The code should be a running service with a single http endpoint for receiving the ‘signal’ to be processed by your application. Easier for your team to understand and debug Easier for your team to maintain and add new signals Easier to test o The code should have appropriate levels of testing to ensure that the stated requirements are met.Requirements
As they mentioned that once in production it is expected that up to 50 new signals will be added per month (600 after year one, 1200 after year two etc), we have added these logics in signal.properties to be dynamically added anytime. During the start we load the signal properties into a map and once we receive a signal, we execute them from the Algo library using reflections.