Currently, the caching of the statistics is made synchronously: when a user makes a GET request on the '/statistics/` endpoint, the current statistics are cached.
This is unreliable since it requires someone to make these requests for us to have a good chronological representation of the statistics over time.
An asynchronous implementation that caches the statistics 1x or 2x a day is needed. Suggestion:
django-q
corn
celery
(can't remember but I'm sure there are others :) )
Currently, the caching of the statistics is made synchronously: when a user makes a GET request on the '/statistics/` endpoint, the current statistics are cached. This is unreliable since it requires someone to make these requests for us to have a good chronological representation of the statistics over time. An asynchronous implementation that caches the statistics 1x or 2x a day is needed. Suggestion: