Practise the standard verbs for batching GraphQL resolvers with DataLoader.
0 / 5 completed
1 / 5
Fill in: 'We ___ a DataLoader instance per request so identical field resolutions within one query get batched into a single call.'
We 'create an instance' — the standard, simple collocation for instantiating a per-request loader. The other options are less idiomatic here.
2 / 5
Fill in: 'Sharing one DataLoader instance across requests can ___ one user's cached data leaking into another user's response.'
We say a shared loader will 'cause' data leakage — the standard collocation for the resulting bug. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ individual key lookups into a single batched database call so a resolver never fires one query per item.'
We 'batch' lookups — the standard, established DataLoader collocation for combining many keys into one call. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ the resulting values in the same order as the input keys so DataLoader can correctly map each result back.'
We 'return' values — the standard, simple collocation for a batch function's expected output shape. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ query counts before and after adding DataLoader to prove the N+1 problem is actually gone, not just hidden.'
We 'compare' counts — the standard, simple collocation for contrasting metrics before and after a change. The other options are less idiomatic here.