René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Include a caching document provider implementation by default","articleBody":"Caching the parsing and validation of a document can save significant latency.\n\nFor very large operations, and tools like Relay produce very large operations, the parse and validate latency can be upwards of 15-20ms (p99)\n\nBy caching this step you can amortize the cost over many requests and hence cut nearly all of this latency out.\n\nThe `graphql.execution.preparsed.PreparsedDocumentProvider` is the interface that allows you to build a caching document mechanism but out of the box graphql-java does not provide a working implementation\n\nI propose that we \n\n* Create a `public class CachingDocumentProvider implements PreparsedDocumentProvider`\n* That is used Caffeine as the cache\n* Provide a GraphQLUnusualConfiguration mechanism to to tune the cache \n  * time base\n  * size based\n  * etc\n* Ship with this TURN on by default (in 2 versions)\n* Shade in https://github.com/ben-manes/caffeine as the cache implementation\n\nThe implication here is that https://github.com/ben-manes/caffeine would become a dependency (shaded) and we have mostly aimed for low to zero dependencies but I think the juice is worth the squeeze here.  All operations will run faster with  a cache in place.\n\nI dont know right now of the implications for library frameworks such as Spring GraphQL.  Do they have one themselves, is it always on?  Hence this issue to stand as a discussion mechanism","author":{"url":"https://github.com/bbakerman","@type":"Person","name":"bbakerman"},"datePublished":"2025-09-02T03:12:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/4107/graphql-java/issues/4107"}