graphql/dataloader
Dataloader
DataLoader is a utility that collects individual data loads into a single batch and caches results to minimize redundant backend requests. It operates on a batch-and-cache architecture, where multiple data lookups within a single execution frame are grouped together and dispatched as one request, with the results stored in memory for instant retrieval on subsequent calls.
The utility distinguishes itself through several key capabilities. It supports per-key error handling, allowing partial failures within a batch without rejecting the entire operation. A cache priming mechanism lets developers pre-populate the cache with known key-value pairs, while explicit cache invalidation methods enable clearing specific keys or the entire cache to force fresh data loads. The cache store is pluggable, allowing the default in-memory Map to be replaced with alternative implementations such as an LRU cache. A scheduler-based dispatch system provides control over when accumulated loads are sent as a batch, supporting manual triggering or delayed execution.
The broader capability surface includes batch data loading, caching data lookups, and custom cache strategies. The documentation covers configuration for customizing batch scheduling and swapping cache stores, as well as methods for loading multiple keys and clearing cached entries.
Features
- Data Batching and Caching Utilities - Collects multiple data loads into a single batch and caches results to reduce backend requests.
- Batched Data Loading - Collects multiple individual data requests into a single batch to reduce backend round trips.
- Request Batching - Collects individual data loads into batches and caches results to minimize redundant backend requests.
- Resolved Value Caching - Cache loaded values in memory so repeated key lookups resolve instantly without a backend call.
- Key-Value Batching - Accepts an array of keys and resolves each to its value or an error, handling partial failures.
- Custom Batch Triggers - Controls when a batch of collected loads is dispatched, enabling manual triggering or delayed execution.
- Cache Priming Mechanisms - Provides a cache priming mechanism to pre-populate the cache with known key-value pairs.
- Cache Priming - Pre-populates the cache with known key-value pairs to avoid unnecessary backend requests for expected data.
- Cache Clearing - Clear cached entries by removing a specific key or the entire cache to force fresh data loads.
- Pluggable Cache Implementations - Replaces the default in-memory cache with alternative implementations like LRU to manage memory.
- Pluggable Cache Stores - Replaces the default in-memory Map with any cache implementation, such as an LRU cache.
- Cache Priming Operations - Primes the cache with known key-value pairs so future loads return immediately without a backend request.
- Cache Invalidation - Provides methods to clear specific keys or the entire cache to force fresh data loads.
- Load Dispatch Schedulers - Uses a custom scheduler to control when accumulated loads are dispatched as a batch.
- Custom Batch Dispatch Schedulers - Controls when batched loads are dispatched through custom schedulers for manual or delayed execution.
- Partial List Error Handling - Resolves each key individually in a batch, allowing partial failures without rejecting the entire batch.
- Pluggable Cache Backends - Allows swapping the default in-memory Map cache with any external cache implementation.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
