Event based cache invalidation in GraphQL
Simone Sanfratello - 3 years ago
Caching is one of the most effective ways to achieve fast performance, probably the main one, but in a GraphQL context it’s not that easy: once we get to caching GraphQL queries in order to speed up our application backend, we also need to refresh the cache.
How can we do that? What are the strategies we can apply to keep our dynamic data ready to use and up to date at the same time?
How can we invalidate the cache efficiently?
Time based invalidation is widely used but not very precise, so let's introduce event based invalidation, with node.js, fastify and mercurius!
Jobs with related skills

Software-Architekt (m/w/d)
Instaffo
·
today
Neuss, Germany

Fullstack-Entwickler (m/w/d) – React, JavaScript, Node.js & AWS Amplify
Instaffo
·
today
Frankfurt am Main, Germany

Senior Expert Softwareentwicklung (m/w/d) für Web Full-Stack
Instaffo
·
today
Chemnitz, Germany

Senior Backend Entwickler Node.js (m/w/d)
Instaffo
·
today
Schalksmühle, Germany
Related Videos