Optimise and Eliminate Redundant Connections to MongoDB

[Pyatakov]

Problem description

Our application is currently establishing approximately 120 connections to the MongoDB server with a clean setup. This high number of connections may be causing unnecessary resource utilization and potential performance issues. While no severe impact has been measured, we want to optimize our database connection management to improve efficiency and prevent future scalability problems. The source of these redundant connections is currently unknown, and our current connection pooling setup needs investigation.

Requirements

• Investigate the source of redundant MongoDB connections in our application.
• Analyse the current MongoDB driver configuration and connection pooling setup.
• Develop a strategy to reduce the number of connections from the current ~120 to a more optimal number.
• Implement the chosen optimisation strategy (e.g., connection pooling, refactoring database access patterns).

Definition of done

• The number of MongoDB connections has been reduced to an optimal level (to be determined during investigation).
• Optimisation changes have been implemented and thoroughly tested.
• Application functionality remains intact with the optimised connections.
• Performance metrics show improvement or no degradation after changes.

Acceptance criteria

• [ ] Optimisation strategy implemented and tested in a non-production environment.
• [ ] Number of MongoDB connections reduced by at least 40% (from ~120 to ~70 or fewer) without impacting application functionality.
• [ ] No new errors or performance regressions introduced as a result of the changes.
• [ ] Performance tests show that the application maintains or improves its current performance levels with the reduced number of connections.