Optimize Donut Chart + Tree Chart Data Retrieval

[eeshabarua]

Description

Currently, the donut chart and tree chart components run a tRPC procedure on every reload, which can lead to performance issues. Optimize the data using a MongoDB aggregation or stored procedure.

Learning Objectives

• Understand MongoDB triggers (MongoDB doesn't have stored procedures)
• Weigh the benefits of Response Caching to speed up retrieval on reload / rerender

Todo

• [ ] Build a response object cache with aggregate Donut / Tree data
• [ ] Add trigger to MongoDB cluster that populates Donut / Tree chart aggregated data cache on db update

Useful Links

• https://www.mongodb.com/basics/aggregation
• https://trpc.io/docs/server/caching
• https://www.mongodb.com/features/stored-procedures

[kennykos]

We should use mongodb triggers instead of a stored procedure. The trigger should execute every time the the relevant collections in the production DB is updated.

Also, it would be nice if we could store these triggers in the repository instead of mongo's website so we could have nice version control and peer review, but that isn't a deal breaker.