Fast cache invalidation for GraphQL with Quell+


Since the launch of QuellQL in 2020, our engineering team has been constantly looking for ways of how we can improve the performance, accuracy, and simplicity of our GraphQL caching solution. Our ongoing efforts have thus far resulted in the development of a cost-effective client- and server-side caching npm library for GraphQL, we doubled the number of our core features, and deployed a live demo on AWS. However, as QuellQL has worked well, GraphQL continues to grow rapidly in numbers and complexity which exposed Quell to cache invalidation issues and revealed performance bottlenecks — if you are thinking about Phil Karlton’s quote, yes we figured how to name things ;)


GraphQL is a powerful, API-based query language that uses queries for data fetching and mutation operations to modify server-side data. GraphQL offers the following types of mutations which allow clients to:

  • update or delete existing data


Server: Building out the cache invalidation feature greatly benefited the accuracy of QuellQL’s core library. However, our testing and benchmark process revealed early on that there was still a lot of performance work left on the server and client-side.

Getting started

We highly encourage you to take your first step towards harnessing the power of cache invalidation along with GraphQL query and mutation request/responses. To get started with QuellQL in your next application, check out all the documentation you need for getting started in, quell-client npm, quell-server npm, and GitHub.

Open-Source & Community Contributions

QuellQL is an open-source product developed under tech accelerator OS Labs, dedicated to creating productivity tools for developers. We welcome contributions and feedback via GitHub, and if you love using QuellQL or you’re just excited by the product, we appreciate each GitHub star that comes our way.

Engineering Team