Backend Infrastructure

Infrastructure diagram

The Backend Monolith service

This is the main communication point from the mobile app, and maintains the entire state of the application other than any PII data (which is stored in the Auth & PII service) and the optimisation engine (which is in the Deep Though service).

The entire service containing multiple API endpoints is hosted on a single Lambda instance using the Zappa framework.

Cron related tasks are handled via AWS EventBridge that calls the specific functions inside the codebase using the Zappa framework.

It is recommended but not necessary to keep reserve capacity, cold start time is at about 5000ms.

Components of the BackendMonolith Service

Financial Plan management

deep_tech module acts as the client for the Deep thought optimisation service and takes care of:

• managing the financial planning questionnaire flows
• managing the financial institution’s default investment policy and client level customisations
• storing the financial plan request objects (the user’s goals/objectives, loans, assets etc. which are used to generate a financial plan)
• storing the output of the Deep thought engine as a structured financial plan
• utilities to visualise the plan in the form of a report
• managing the investment checklists for users to help them invest according to the plan directly on the app

BSEStAR Mutual Fund transaction platform

• integration_bsestar package that contains the client side code to call BSEStAR APIs
• bse_dashboard to contain the order management logic for Mutual Funds, which uses the client side code from the integration_bsestar package
• PII data related to clients is stored in the Auth service, and is pulled by service to service calls made by BackendMonolith as and when required