-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Automatic Persisted Queries #734
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This implementation will work only with single graphql server instance or sticky sessions.
With load-balancing follow-up query can land on a different server, so it will take some until all servers will receive APQ hash.
I would suggest doing interface to support pluggable implementation (e.g. shared redis cache).
I would suggest doing interface to support pluggable implementation
See DBL-Lee#1 for proposed implementation |
Support for external APQ cache
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
this looks solid 👍 |
Thanks for the PR. I gave it a test run on one of our projects, docs are good, everything seems to work. The handler package is becoming a bit big, we will have to do something to make it a bit more modular in the future. |
Automatic Persisted Queries
This PR implements automatic persisted queries as described here
It follows apollo server implementation here to make sure it is compatible with apollo clients.
This have been running in our production environment for a few weeks and works well with Apollo client with APQ enabled.
This implements #401
I have: