DataLoader integration in NestJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import DataLoader in a NestJS service.

NestJS

import [1] from 'dataloader';

Drag options to blanks, or click blank then click option'

ADataLoad

BLoaderData

CDataLoader

DLoader

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect import names like 'LoaderData' or 'DataLoad'.

Forgetting to import DataLoader before using it.

You need to import DataLoader exactly as it is exported from the 'dataloader' package.

2fill in blank

medium

Complete the code to create a new DataLoader instance in a NestJS service.

NestJS

const userLoader = new DataLoader([1]);

Drag options to blanks, or click blank then click option'

AbatchLoadFn

BbatchLoaderFn

CloadBatchFn

DbatchLoadFunction

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect property names like 'batchLoadFunction' or 'loadBatchFn'.

Passing the batch function directly without wrapping in an object.

The DataLoader constructor expects an object with a batchLoadFn property that is a function to batch load keys.

3fill in blank

hard

Fix the error in the batch loading function signature for DataLoader.

NestJS

async function batchLoadUsers([1]) { return users; }

Drag options to blanks, or click blank then click option'

Akey

Bkeys

CuserIds

Dids

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular names like 'key' which is not an array.

Using unrelated parameter names that confuse the function purpose.

The batch loading function receives an array of keys, commonly named keys.

4fill in blank

hard

Fill both blanks to create a DataLoader that batches user IDs and returns users.

NestJS

const userLoader = new DataLoader(async ([1]) => {
  const users = await this.userService.findByIds([2]);
  return [1].map(id => users.find(user => user.id === id));
});

Drag options to blanks, or click blank then click option'

Akeys

BuserIds

Attempts:

3 left

💡 Hint

Common Mistakes

Using inconsistent variable names between parameter and service call.

Not mapping keys to users correctly.

The batch function receives keys and passes userIds to the service. Then it maps keys to the found users.

5fill in blank

hard

Fill all three blanks to use DataLoader in a NestJS resolver method to load a user by ID.

NestJS

async getUser(id: string) {
  const user = await this.[1].load([2]);
  return user ? [3] : null;
}

Drag options to blanks, or click blank then click option'

AuserLoader

Bid

Cuser

DuserService

Attempts:

3 left

💡 Hint

Common Mistakes

Calling load on the service instead of the DataLoader.

Returning the wrong variable or forgetting to check for null.

The method calls userLoader.load(id) and returns the loaded user or null.

Practice

1. What is the main purpose of using DataLoader in a NestJS application?

easy

A. To handle HTTP routing and middleware

B. To serve static files efficiently

C. To manage database schema migrations

D. To batch and cache multiple data requests to improve performance

Solution

1. Step 1: Understand DataLoader's role

   DataLoader is designed to batch and cache data fetching operations to reduce redundant calls.

2. Step 2: Compare with other options

   Options A, C, and D relate to other NestJS features, not DataLoader's purpose.

3. Final Answer:

   To batch and cache multiple data requests to improve performance -> Option D

4. Quick Check:

   DataLoader = batch + cache [OK]

Hint: DataLoader batches requests to avoid repeated fetching [OK]

Common Mistakes:

• Confusing DataLoader with routing or middleware
• Thinking DataLoader manages database migrations
• Assuming DataLoader serves static files

2. Which of the following is the correct way to create a DataLoader instance inside a NestJS service?

easy

A. const loader = new DataLoader(batchFunction());

B. const loader = DataLoader.create(batchFunction);

C. const loader = new DataLoader(keys => batchFunction(keys));

D. const loader = DataLoader(batchFunction);

Solution

1. Step 1: Recall DataLoader instantiation syntax

   DataLoader is instantiated with new DataLoader(batchFunction), where batchFunction is a function receiving keys.

2. Step 2: Analyze options

   const loader = new DataLoader(keys => batchFunction(keys)); correctly uses new DataLoader(keys => batchFunction(keys)). Options B, C, and D use incorrect syntax or call batchFunction immediately.

3. Final Answer:

   const loader = new DataLoader(keys => batchFunction(keys)); -> Option C

4. Quick Check:

   Use new DataLoader(batchFunction) [OK]

Hint: Use 'new DataLoader' with a batch function callback [OK]

Common Mistakes:

• Calling batchFunction immediately instead of passing it
• Using DataLoader as a function without 'new'
• Using a non-function argument

3. Given the following batch function in a NestJS DataLoader service:

async function batchUsers(ids: readonly number[]) {
  return ids.map(id => ({ id, name: `User${id}` }));
}

What will be the output of await loader.load(2) if loader is created with this batch function?

medium

A. { id: 2, name: 'User2' }

B. [{ id: 2, name: 'User2' }]

C. undefined

D. Error: batch function must return array of same length

Solution

1. Step 1: Understand batch function output

   The batch function returns an array of user objects matching the input ids in order.

2. Step 2: Understand loader.load behavior

   loader.load(2) returns a single user object corresponding to id 2, not an array.

3. Final Answer:

   { id: 2, name: 'User2' } -> Option A

4. Quick Check:

   load(id) returns single item from batch array [OK]

Hint: load() returns one item, batch returns array [OK]

Common Mistakes:

• Expecting load() to return an array
• Confusing batch function return with load return
• Assuming batch function returns undefined

4. You wrote this batch function for DataLoader:

async function batchPosts(ids: readonly number[]) {
  const posts = await getPostsByIds(ids);
  return posts;
}

But you get wrong results when loading posts. What is the likely problem?

medium

A. The returned array posts is not in the same order as ids

B. The batch function should not be async

C. You must return a Map instead of an array

D. The function should return a Promise of a single post, not an array

Solution

1. Step 1: Check batch function contract

   DataLoader requires the batch function to return results in the same order as the keys array.

2. Step 2: Analyze getPostsByIds behavior

   If getPostsByIds returns posts unordered, the batch function breaks this contract causing wrong results.

3. Final Answer:

   The returned array posts is not in the same order as ids -> Option A

4. Quick Check:

   Batch function must preserve order [OK]

Hint: Batch function output order must match input keys order [OK]

Common Mistakes:

• Ignoring order of returned array
• Thinking batch function can't be async
• Returning Map instead of array

5. In a NestJS GraphQL resolver, you want to integrate DataLoader to batch user requests per HTTP request. Which approach correctly ensures a new DataLoader instance is created for each request to avoid caching issues across users?

hard

A. Create a DataLoader instance once in the module constructor

B. Create a DataLoader instance inside a request-scoped provider injected into the resolver

C. Create a single global DataLoader instance as a singleton service

D. Use a static DataLoader instance shared across all requests

Solution

1. Step 1: Understand DataLoader caching scope

   DataLoader caches results per instance, so sharing one instance globally causes cross-request data leaks.

2. Step 2: Use request-scoped provider

   Creating a DataLoader instance per request via a request-scoped provider ensures isolated caches per user request.

3. Final Answer:

   Create a DataLoader instance inside a request-scoped provider injected into the resolver -> Option B

4. Quick Check:

   Request-scoped DataLoader avoids cross-request cache [OK]

Hint: Use request-scoped provider for per-request DataLoader [OK]

Common Mistakes:

• Using singleton DataLoader causing shared cache
• Creating DataLoader once in module constructor
• Using static instance shared globally