Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caching considerations #17

Open
CasperWA opened this issue Feb 11, 2021 · 0 comments
Open

Caching considerations #17

CasperWA opened this issue Feb 11, 2021 · 0 comments
Labels
Caching Issue or PR related to caching enhancement New feature or request question Further information is requested

Comments

@CasperWA
Copy link
Member

Should we cache the results returned from a gateway's databases according to the query?
If yes, this could be done in different ways, either on a per gateway basis, or in a Mongo collection per database or similar that each gateway can then query. The latter would not demand as much space, and is to be preferred.
We would need to ensure the same result can be found regardless of the order of the query parameters.
Persistence time?

What is the level of caching that should eventually be implemented?
We could simply only cache meta data, like data_available, etc., or cache whole entries/responses from each database.

Gateway response caching.
For the expected POST endpoints for querying gateways, how long should the responses be cached for to be re-retrieved?
Should regular GET query requests to gateways also be cached?

@CasperWA CasperWA added enhancement New feature or request question Further information is requested Caching Issue or PR related to caching labels Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Caching Issue or PR related to caching enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant