With the right cache key strategy we should be able to avoid generating exports of e.g. yearly historic stats per club, it does require that adequate cache key for invalidating cache.
Proposed cache level is on the csv file, introducing a yearly level and a club level key so these are only generated once.
The key for invalidation could come from e.g. the last change date of any flight within that flight year.
We should consider the cross club export option, at this point it the year level across all clubs is timing out, if we want to support it we should operate on the cache layer and aggregate the cached files for each yearly club exports at this level and not generate anything, simply aggregate... or consider removing the option of exporting when the range will lead to an operation timeout.
With the right cache key strategy we should be able to avoid generating exports of e.g. yearly historic stats per club, it does require that adequate cache key for invalidating cache.
Proposed cache level is on the csv file, introducing a yearly level and a club level key so these are only generated once. The key for invalidation could come from e.g. the last change date of any flight within that flight year.
We should consider the cross club export option, at this point it the year level across all clubs is timing out, if we want to support it we should operate on the cache layer and aggregate the cached files for each yearly club exports at this level and not generate anything, simply aggregate... or consider removing the option of exporting when the range will lead to an operation timeout.