graphql-compose-elasticsearch
graphql-compose-elasticsearch copied to clipboard
Question: Client side cache growth
Hi,
I was wondering how to deal with the potential growth of the client cache based on different parameters. I could think in:
- Create a new graphql client whti no cache used only for searches.
- Skip the cache for search queries.
What's your advise here?
Thanks
Frankly no exact advice. Too few income data for the proper answer.
Anyway, you need to to find a solution for resetting the cache (via timeout, number of records, size of memory, or via some interval time).