Question 1

How to use BatchLoader with GraphQL Ruby?

Accepted Answer

Use BatchLoader::GraphQL.for with object IDs in your resolvers and add use BatchLoader::GraphQL in your schema setup. The README provides a complete example, including lazy_resolve integration for automatic batching.

Question 2

BatchLoader vs shopify/graphql-batch: which is better?

Accepted Answer

BatchLoader is more generic and Ruby-idiomatic, using lazy objects without Promises, while graphql-batch is GraphQL-specific with Promise-based async. Choose BatchLoader for flexibility across REST and GraphQL, or graphql-batch if you prefer a GraphQL-first, order-preserving approach.

Question 3

How to disable caching in BatchLoader for tests?

Accepted Answer

Set cache: false in the batch method call. This ensures fresh data in test environments or after mutations, but you should also consider setting replace_methods: false to avoid method replacement issues.

Question 4

Can BatchLoader handle concurrent HTTP requests?

Accepted Answer

Yes, it's thread-safe and can be combined with gems like parallel to execute HTTP requests concurrently in threads. The README shows an example where HttpClient requests are batched and run in parallel, leveraging MRI's GIL release.

Question 5

How to clear BatchLoader cache between Rails requests?

Accepted Answer

Add config.middleware.use BatchLoader::Middleware to your application configuration. This middleware automatically clears the cache after each request, preventing stale data from persisting across HTTP cycles.

Question 6

What's the default value for missing records in BatchLoader?

Accepted Answer

It defaults to nil for missing items, but you can specify a custom default_value in the batch method, such as NullUser.new, to return a placeholder object instead, as shown in the Loading multiple items section.

batch-loader

What is batch-loader?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions