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
Hey, I'm meshing multiple graphql endpoints and using a redis cache via the response caching plugin. I'm trying to figure out the right way to invalidate cache entries for my scenario:
What I'm meshing are subgraphs from The Graph, which index blockchain data, and so I don't have an access to the DBs themselves
The graphql endpoints don't have mutations so invalidating via mutation is not relevant
My current thinking is listening to relevant smart contract events and then deleting the associated entries on the cache. I don't see a way to invalidate programmatically when using the mesh, something like in the image below. Is there another recommended way to handle that?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey, I'm meshing multiple graphql endpoints and using a redis cache via the response caching plugin. I'm trying to figure out the right way to invalidate cache entries for my scenario:
My current thinking is listening to relevant smart contract events and then deleting the associated entries on the cache. I don't see a way to invalidate programmatically when using the mesh, something like in the image below. Is there another recommended way to handle that?
Beta Was this translation helpful? Give feedback.
All reactions