graphql-compose / graphql-compose/graphql-compose-elasticsearch
Question: Client side cache growth
Open
- Dominant language
- TypeScript
- Stars
- 584
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I was wondering how to deal with the potential growth of the client cache based on different parameters.
I could think in:
1. Create a new graphql client whti no cache used only for searches.
2. Skip the cache for search queries.
What's your advise here?
Thanks
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.