Best practices for caching hasura responses in redis?

I was wondering whether there are any officially recommended patterns for caching hasura responses to a redis instance. Couldn't find any documentation/open issues/blog posts talking about this, here's what I have in mind: 1. Run a core server (for caching, auth) alongside hasura as a microservice 2. Add a middleware to intercept any graphql requests 3. Check if the exact request exists in redis, if so return (or whatever caching logic) 4. Otherwise, ask hasura microservice to generate a new response, cache that and then send to client

Posted by Aditya94A on May 4, 2020, 12:41 PM

Tags

• github (Sysadmin)

Related issues

• Custom games stuck on "finding server" for all european servers
• Feature request: add ACP (Agent Client Protocol) stdio JSON-RPC mode
• Forza Horizon 6 (2483190)
• Turn off integrated browser for default
• Weekly updates are too frequent
• [BUG] Max 20x plan: 100% usage after 2 hours of light work (5 commits, no agents)