put in place the cache for a reasonable first selection of endpoints
think through a refresh policy for these endpoints
2 (above) needs to balance (presumably) too much burden on the databases versus the initial experience when the app loads. @harryjmoss : is it the case that on first load if the cache is older than the max-age parameter it will force a fresh call? If so then I assume the refresh has to be less than max-age on first load? Or we need some approach to the interface such that it starts loading whilst the user is looking elsewhere?
Aims for this pull request are
2 (above) needs to balance (presumably) too much burden on the databases versus the initial experience when the app loads. @harryjmoss : is it the case that on first load if the cache is older than the
max-age
parameter it will force a fresh call? If so then I assume the refresh has to be less thanmax-age
on first load? Or we need some approach to the interface such that it starts loading whilst the user is looking elsewhere?