Use @GraphQLContext for batching without @Batched about graphql-spqr HOT 2 CLOSED

@Batched in SPQR provides the same semantics as that annotation already provides in graphql-java (note that it belongs to a graphql-java package, not SPQR). It provides a simple batching model that maps well to SQL (and some other) backends. It works with BatchedExecutionStrategy only.

Dataloader offers a very different strategy. To use dataloader, you must write the batch loader functions yourself and then change your logic to fetch data through the dataloader instead of directly. Unlike the previous model, it's not down to the execution strategy, but down to how you write your datafetchers. SPQR doesn't know what your methods do, so you need to change your own code to use the dataloader.

You might want to create a DataLoaderRegistry per request, and stick into the global context. This way you can easily inject it into your resolver methods via @GraphQLRootContext. Or, since you're using Spring, make DataLoaderRegistry a request scoped bean that you inject into your service classes.
You must also make sure to register a DataLoaderDispatcherInstrumentation to dispatch the batch jobs. But this is all completely external to SPQR.

Keep in mind, SPQR only really deals with assembling the schema and wiring your methods as datafetchers. Actually executing the queries you do using graphql-java directly.

from graphql-spqr.

You can see a simple example of using @Batched in BatchingTest

from graphql-spqr.