Software
10-03-25:
Decision: Let Selenium be process run separately
Reason: Even though selenium grid reduces the chrome workload the script still waits for the response from the selenium grid as it may become a bottle neck and will have workload on the production
15-03-25:
Decision: Spoof the record near the database its
Status: Onhold
Reason: There is a way where we can easily generate csv file in query, but this file is in the MariaDB data disk need to mount the disk with the application
Impedance: As the namespace of the data disk and file share is different need to change the namespace
24-03-25:
Decision: To separate PowerBI dashboard into financial and historical reports
Status: Stopped
Reason: We assumed separating the reports will lower the load to the database as financial reports only required the current year data, but PowerBI always load all the data from the database into the power Query editor even when we sperate this will not reduce the load
28-03-25:
Decision: Stop Checklist and remove the file records
Reason: As there is a view change in the check list need is not necessary and file records is kept only for the checklist
03-04-25:
Decision: Report Configuration changes should always be done through fixture
Reason: As there is a customer complain that while changing an old report, we missed a column
04-04-25:
Decision: In transformer bot should be run separately
Status: Onhold (14-05-25)
Reason:
As the bot file are uploaded immediately after downloading this will block the manual advice loaded by the customer and need to see results as fast as they can
As the Transformer is Fast now due to direct data injection to MariaDB
Decision: To directly inject data into MariaDB in transformer
Reason: As it is very fast compared to Frappe ORM
29-04-25:
Decision: Instead of pgchameleon for mariadb to postgres sync we Airbyte
Reason: As Airbyte provide various functionality and intuitive UI and have many connector
05-05-25:
Decision: OLAP data is always t-1
Reason: Since the reports are financial reports and does not require the real time data.
05-05-25:
Decision: 10PM - 11PM Scheduled maintenance every day
Reason: It will be helpful for us to maintain the database and service restart
05-05-25:
Decision: PostgreSQL is to be set as the OLAP database instead of MariaDB
Reason: As PostgreSQL support materialized view and have additional features
07-05-25:
Decision: Unit Test case writing is stopped instead Need to work on flow test
Reason: As unit testing will needed to be change while change the code with same functionality, so we are going to functional testing
14-05-25:
Decision: For functional Testing We are going to use Roboto framework
Reason: As Roboto Is User friendly, prebuild report and most widely used
14-05-25:
Decision: Using Job for running Roboto Framework
Reason: To Enable parallelization in Testing
Cloud
01-03-25:
Decision: To Create specific pod for only reports
Reason: As the report's generation takes time the Oom of the Kubernetes died due to the load so an additional pod only dedicated for the report downloading with the proper resource is allocated
06-03-24
Decision: Azure Backup Vault retention policy setup for 30 days
Reason: The Approx. cost of the backup is differ around 100-200 rupees for the retention of 7-30 days