impact-graph
impact-graph copied to clipboard
Optimize Analytics Tracking Calls
This is a Quality of Life change. Right now Analytics tracking methods are being called in the main code/mutations, this is an issue because it slows down the backend from answering the frontend and if the tracking break, it breaks the whole code.
Solutions:
- Refactor Tracking calls into it's own module / methods / classes so it's not spread out through the whole code base.
- Move tracking calls to a background Job that it's executed after the backend answers the frontend.