Today we are thrilled to announce the public beta release of Partial Query Caching! Since our alpha release in October, we have been hard at work improving and refining this groundbreaking feature to give you the best edge caching solution for GraphQL.
Partial Query Caching addresses the limitations of existing GraphQL caching solutions by automatically splitting queries based on individual cache configurations for GraphQL types and fields. This innovative approach allows for more efficient caching, significantly increasing the amount of cached data and reducing origin traffic. The result is improved stability and reduced infrastructure costs.
Notable Improvements in the Public Beta Release
We have made significant improvements to Partial Query Caching based on user feedback and internal testing. Here are some of the notable improvements we have shipped since the alpha version:
Our dashboard now provides a comprehensive view of all the important details about Partial Query Caching. You can easily debug cache entries after sending a query in GraphiQL, view cache entries for individual requests in detail, and preview cache entries based on the latest cache configuration.
Enhanced Algorithm and Bug Fixes
We have addressed numerous bugs in our query splitting algorithm and implemented additional safeguards to ensure correct caching behavior. We have particularly focused on queries inside fields that return a list of entities where the ordering might be non-deterministic.
Integration with Cache Guard
Partial Query Caching is now seamlessly integrated with Cache Guard, one of our most important features that will give you confidence in changes you make to your cache configuration. You will now see how such changes affect existing operations and how they are split up. Gain full visibility and control over your cache configuration with this powerful combination.
To help you adopt and leverage the power of Partial Query Caching, we have released the first version of public documentation. This documentation provides an overview of how Partial Query Caching works and offers guidance on how to effectively utilize this feature.
Last but not least, enabling Partial Query Caching with Stellate for your GraphQL API is now publicly available. Instead of feature-flagging it, we now invite everyone to easily enable the feature using a new setting in the Stellate config. Take advantage of the efficiency and performance benefits that Partial Query Caching provides with just a single step.
Start optimizing your cache today!
We invite you to join us in the public beta and experience the power of Partial Query Caching for yourself. If you haven’t yet, sign up now and take advantage of more efficient caching, reduced origin traffic, and improved performance.
To learn more about Partial Query Caching and how to enable it for your GraphQL API, visit our documentation or reach out to our support team for assistance.
We are committed to continually refining and enhancing this feature based on your feedback, so please don't hesitate to share your thoughts and suggestions.