Pagination patterns in Node.js - Step-by-Step Execution

Concept Flow - Pagination patterns

Start Request with page & limit

↓

Calculate offset = (page-1)*limit

↓

Query database with offset & limit

↓

Receive subset of data

↓

Send data + pagination info

↓

Client displays current page data

↓

User clicks next/prev page

↩Back to Start Request

This flow shows how pagination works by calculating which data slice to fetch and then displaying it, looping as user navigates pages.

Execution Sample

Node.js

const page = 2;
const limit = 3;
const offset = (page - 1) * limit;
const data = allItems.slice(offset, offset + limit);
console.log(data);

This code fetches the second page of data with 3 items per page from a list.

Execution Table

Step	Variable	Value	Action	Output
1	page	2	Set current page
2	limit	3	Set items per page
3	offset	(2-1)*3=3	Calculate offset
4	data	allItems.slice(3,6)	Slice data from index 3 to 5	[item4, item5, item6]
5	console.log		Print data	[item4, item5, item6]
6	-	-	End of pagination fetch	No more steps

💡 All steps done, data for page 2 with limit 3 fetched and displayed

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
page	undefined	2	2	2	2	2
limit	undefined	undefined	3	3	3	3
offset	undefined	undefined	undefined	3	3	3
data	undefined	undefined	undefined	undefined	[item4, item5, item6]	[item4, item5, item6]

Key Moments - 3 Insights

Why do we calculate offset as (page - 1) * limit?

Because pages start at 1, but array indexes start at 0, so offset shifts to correct start index. See execution_table step 3.

What happens if page is 1?

Offset becomes 0, so data slice starts from the beginning. This is shown by the formula in step 3.

Why do we slice from offset to offset + limit?

To get exactly 'limit' number of items starting at offset. See step 4 where slice(3,6) gets 3 items.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of offset at step 3?

A 3

B 2

C 6

D 0

💡 Hint

Check the 'Value' column in step 3 of execution_table

At which step is the data slice created?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look for the action 'Slice data' in execution_table

If limit changes to 5, how does the slice range change at step 4?

A slice(3,6)

B slice(2,7)

C slice(3,8)

D slice(0,5)

💡 Hint

Offset stays 3, slice ends at offset + limit, see variable_tracker for limit

Concept Snapshot

Pagination fetches a subset of data by:
1. Setting page number and items per page (limit)
2. Calculating offset = (page-1)*limit
3. Slicing data from offset to offset+limit
4. Returning this slice for display
This pattern helps load data in chunks for better performance.

Full Transcript

Pagination patterns in Node.js involve calculating which part of a data list to show based on the current page and how many items per page. We start by setting the page number and limit. Then we calculate the offset by multiplying (page minus one) by the limit. This offset tells us where to start slicing the data array. We slice from offset to offset plus limit to get the current page's items. Finally, we send this slice to the client to display. This process repeats as the user navigates pages, fetching only the needed data each time.

Practice

1.

What is the main purpose of pagination in a Node.js application?

easy

A. To combine all data into one large response

B. To split large data into smaller pages for faster loading and better user experience

C. To delete old data automatically

D. To encrypt data before sending it to the client

Solution

1. Step 1: Understand pagination concept

   Pagination divides data into smaller chunks or pages to avoid loading everything at once.

2. Step 2: Identify the benefit in Node.js apps

   This improves speed and usability by sending only a subset of data per request.

3. Final Answer:

   To split large data into smaller pages for faster loading and better user experience -> Option B

4. Quick Check:

   Pagination = split data for speed [OK]

Hint: Pagination means splitting data into pages for faster loading [OK]

Common Mistakes:

• Thinking pagination deletes data
• Confusing pagination with encryption
• Assuming pagination combines all data

2.

Which of the following is the correct way to use limit and offset for pagination in a SQL query within Node.js?

SELECT * FROM users ORDER BY id ASC LIMIT ? OFFSET ?;

easy

A. limit = number of items per page, offset = (page number - 1) * number of items per page

B. limit = page number, offset = number of items per page

C. limit = total items, offset = 0

D. limit = number of items per page, offset = page number

Solution

1. Step 1: Understand limit and offset roles

   Limit controls how many items to fetch; offset skips items before starting.

2. Step 2: Calculate offset for pagination

   Offset should skip items from previous pages: (page number - 1) * items per page.

3. Final Answer:

   limit = number of items per page, offset = (page number - 1) * number of items per page -> Option A

4. Quick Check:

   Offset skips previous pages = (page-1)*limit [OK]

Hint: Offset skips previous pages: (page-1) times limit [OK]

Common Mistakes:

• Using offset as page number directly
• Swapping limit and offset values
• Setting offset to page number without calculation

3.

Given this Node.js code snippet using a database query for pagination:

const page = 3;
const limit = 10;
const offset = (page - 1) * limit;
const results = await db.query('SELECT * FROM products ORDER BY id ASC LIMIT ? OFFSET ?', [limit, offset]);
console.log(results.length);

If the database has 25 products, what will results.length print?

medium

A. 25

B. 10

C. 15

D. 5

Solution

1. Step 1: Calculate offset and limit values

   Page 3 means offset = (3-1)*10 = 20, limit = 10.

2. Step 2: Determine how many products remain after offset

   There are 25 products total, offset 20 skips first 20, leaving 5 products.

3. Final Answer:

   5 -> Option D

4. Quick Check:

   Remaining items after offset = 5 [OK]

Hint: Last page may have fewer items than limit [OK]

Common Mistakes:

• Assuming full limit items always returned
• Calculating offset incorrectly
• Ignoring total number of products

4.

Identify the error in this Node.js pagination code snippet:

const page = 0;
const limit = 10;
const offset = page * limit;
const results = await db.query('SELECT * FROM items LIMIT ? OFFSET ?', [limit, offset]);

What is the problem with this code?

medium

A. Offset should be negative for first page

B. Limit should be zero to fetch all items

C. Page number should start from 1, not 0, causing incorrect offset

D. Query syntax is invalid with placeholders

Solution

1. Step 1: Check page number usage

   Page is set to 0, but pagination usually starts at 1.

2. Step 2: Calculate offset impact

   Offset = 0 * 10 = 0, so it fetches first page, but page 0 is invalid logically.

3. Final Answer:

   Page number should start from 1, not 0, causing incorrect offset -> Option C

4. Quick Check:

   Page numbering starts at 1 [OK]

Hint: Page numbers start at 1, not 0 [OK]

Common Mistakes:

• Using page 0 as valid page
• Setting limit to zero incorrectly
• Misunderstanding offset calculation

5.

You want to implement cursor-based pagination in Node.js for a real-time chat app. Which approach is best to fetch the next page of messages?

// Current last message ID is stored in lastMessageId
const query = 'SELECT * FROM messages WHERE id < ? ORDER BY id DESC LIMIT ?';
const results = await db.query(query, [lastMessageId, limit]);

Why is this approach better than using offset?

hard

A. Cursor pagination avoids skipping items and handles new data better than offset

B. Offset pagination is faster for real-time data

C. Cursor pagination requires less code but is less reliable

D. Offset pagination works better with unordered data

Solution

1. Step 1: Understand cursor pagination

   Cursor uses a unique ID to fetch next items after the last seen message.

2. Step 2: Compare with offset pagination

   Offset can skip or repeat items if data changes during pagination; cursor avoids this.

3. Final Answer:

   Cursor pagination avoids skipping items and handles new data better than offset -> Option A

4. Quick Check:

   Cursor = stable pagination with changing data [OK]

Hint: Cursor uses last ID to avoid skipping new data [OK]

Common Mistakes:

• Thinking offset is better for real-time data
• Assuming cursor is less reliable
• Confusing cursor with offset usage