You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! We are in the process of setting the Schema Registry for our federated gateway. It's been fairly easy and straightforward so far.
It appears that Redis is only ever used by the persisted_queries utility. If this endpoint/type is never used, then there is no need to have Redis running alongside the schema registry.
It is also not clear from the documentation how this endpoint is meant to be used, as the APQ option in Apollo does not include a REST or separate GraphQL API as an option for a cache layer. I'm not really sure what the use case is for this endpoint.
At any rate, the service is able to run without Redis, but calling the persisted_queries results in the request timing out. Perhaps we could have a flag to exit early from that endpoint and return a 404?
Thank you!
The text was updated successfully, but these errors were encountered:
hey.
You are right, redis is not critical dependency and can be ommited.
Automatic persisted are an apollo feature and yes, we don't have an example how exactly to use it. But basically, you can pass custom class to apollo server that will implement cache get/set and instead of using redis, it can make requests to schema-registry that would manage these things.
You can make a PR to ignore redis in those endpoints. It was meant for performance (to avoid going to DB)
Hello! We are in the process of setting the Schema Registry for our federated gateway. It's been fairly easy and straightforward so far.
It appears that Redis is only ever used by the
persisted_queries
utility. If this endpoint/type is never used, then there is no need to have Redis running alongside the schema registry.It is also not clear from the documentation how this endpoint is meant to be used, as the APQ option in Apollo does not include a REST or separate GraphQL API as an option for a cache layer. I'm not really sure what the use case is for this endpoint.
At any rate, the service is able to run without Redis, but calling the
persisted_queries
results in the request timing out. Perhaps we could have a flag to exit early from that endpoint and return a 404?Thank you!
The text was updated successfully, but these errors were encountered: