Limit and pagination in DynamoDB - Step-by-Step Execution

Concept Flow - Limit and pagination

Start Query

↓

Set Limit N

↓

Fetch up to N items

↓

Check if More Items

Yes No↓

Return Items

↓

Save LastEvaluatedKey

↓

Use LastEvaluatedKey for Next Query

The query fetches up to a set limit of items, checks if more items exist, and if so, saves a key to fetch the next page.

Execution Sample

DynamoDB

Query with Limit=3
Fetch first 3 items
Check LastEvaluatedKey
Use it for next page

This query fetches 3 items from a DynamoDB table and prepares for pagination if more items exist.

Execution Table

Step	Action	Limit	Items Fetched	LastEvaluatedKey	More Items?
1	Start Query	3	0	null	Yes
2	Fetch up to Limit	3	[Item1, Item2, Item3]	Key3	Yes
3	Return first page	3	[Item1, Item2, Item3]	Key3	Yes
4	Use LastEvaluatedKey for next query	3	0	Key3	Yes
5	Fetch next 3 items	3	[Item4, Item5]	null	No
6	Return second page	3	[Item4, Item5]	null	No
7	No more items, end pagination	3	N/A	null	No

💡 No more items to fetch, LastEvaluatedKey is null, pagination ends.

Variable Tracker

Variable	Start	After Step 2	After Step 5	Final
Limit	3	3	3	3
Items Fetched	[]	[Item1, Item2, Item3]	[Item4, Item5]	[Item4, Item5]
LastEvaluatedKey	null	Key3	null	null
More Items?	Yes	Yes	No	No

Key Moments - 3 Insights

Why does the query return fewer items than the limit on the second page?

Because the table has only 5 items total, the second fetch returns only 2 items. This is shown in execution_table row 5 where only 2 items are fetched even though the limit is 3.

What does LastEvaluatedKey represent and why is it important?

LastEvaluatedKey marks the last item fetched and is used to continue fetching the next page. In execution_table rows 2 and 4, it is saved and used to fetch the next set of items.

When does pagination stop?

Pagination stops when LastEvaluatedKey is null, meaning no more items to fetch. This is shown in execution_table row 7 where the process ends.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of LastEvaluatedKey after the first fetch?

A Key3

B null

C Key5

D Item3

💡 Hint

Check the 'LastEvaluatedKey' column in row 2 of the execution_table.

At which step does the query fetch fewer items than the limit?

A Step 2

B Step 5

C Step 3

D Step 6

💡 Hint

Look at the 'Items Fetched' column and compare with 'Limit' in the execution_table.

If the table had 10 items, how would the 'More Items?' value change after step 6?

A It would be 'No'

B It would be 'null'

C It would be 'Yes'

D It would be 'Key10'

💡 Hint

Refer to the 'More Items?' column and understand that more items exist if total items exceed fetched items.

Concept Snapshot

DynamoDB Limit and Pagination:
- Use Limit to fetch up to N items per query.
- If more items exist, LastEvaluatedKey is returned.
- Use LastEvaluatedKey in next query to get next page.
- Pagination ends when LastEvaluatedKey is null.
- Helps manage large datasets in small chunks.

Full Transcript

This visual execution shows how DynamoDB handles Limit and pagination. The query starts with a Limit of 3 items. It fetches the first 3 items and returns them with a LastEvaluatedKey indicating more items exist. Using this key, the next query fetches the next set of items. When fewer items than the limit are returned and LastEvaluatedKey is null, pagination ends. Variables like Limit, Items Fetched, LastEvaluatedKey, and More Items? change step-by-step to track progress. Key moments clarify why fewer items may be returned and how pagination stops. The quiz tests understanding of these steps and variable values.

Practice

1. What does the Limit parameter do in a DynamoDB query or scan?

easy

A. It filters items based on a condition.

B. It sets the maximum size of each item returned.

C. It limits the number of items returned in one response.

D. It sorts the items in ascending order.

Solution

1. Step 1: Understand the role of Limit in DynamoDB

   The Limit parameter controls how many items DynamoDB returns in a single query or scan response.

2. Step 2: Differentiate Limit from other parameters

   Limit does not filter or sort items; it only restricts the count of items returned at once.

3. Final Answer:

   It limits the number of items returned in one response. -> Option C

4. Quick Check:

   Limit = number of items returned [OK]

Hint: Limit sets max items per response, not filtering or sorting [OK]

Common Mistakes:

• Confusing Limit with filtering conditions
• Thinking Limit sorts the results
• Assuming Limit changes item size

2. Which of the following is the correct way to specify a limit of 5 items in a DynamoDB query using AWS SDK for JavaScript?

easy

A. query({ TableName: 'MyTable', MaxResults: 5 })

B. query({ TableName: 'MyTable', Limit: 5 })

C. query({ TableName: 'MyTable', MaxItems: 5 })

D. query({ TableName: 'MyTable', limit: 5 })

Solution

1. Step 1: Check parameter case sensitivity in AWS SDK

   In AWS SDK for JavaScript, parameter names are case-sensitive and 'Limit' must be capitalized.

2. Step 2: Verify correct parameter name for limiting items

   The correct parameter to limit items is 'Limit', not 'limit', 'MaxItems', or 'MaxResults'.

3. Final Answer:

   query({ TableName: 'MyTable', Limit: 5 }) -> Option B

4. Quick Check:

   Correct case and name for limit is 'Limit' [OK]

Hint: Use exact 'Limit' with capital L in query parameters [OK]

Common Mistakes:

• Using lowercase 'limit' instead of 'Limit'
• Using wrong parameter names like MaxItems
• Confusing limit with max results

3. Given a DynamoDB table with 10 items, what will be the result of this scan operation?

scan({ TableName: 'MyTable', Limit: 3 })

medium

A. Returns all 10 items in one response.

B. Returns exactly 3 items in the response.

C. Returns an error because Limit is too small.

D. Returns 3 items and a LastEvaluatedKey for next page.

Solution

1. Step 1: Understand Limit effect on scan results

   Limit restricts the number of items returned in one response to 3.

2. Step 2: Recognize pagination behavior with LastEvaluatedKey

   Since there are more items (10 total), DynamoDB returns 3 items plus a LastEvaluatedKey to continue scanning next items.

3. Final Answer:

   Returns 3 items and a LastEvaluatedKey for next page. -> Option D

4. Quick Check:

   Limit 3 + more items = partial results + LastEvaluatedKey [OK]

Hint: Limit returns partial items plus LastEvaluatedKey if more exist [OK]

Common Mistakes:

• Assuming all items return ignoring Limit
• Thinking Limit causes error if small
• Missing LastEvaluatedKey for pagination

4. You run this DynamoDB query but get an error:

query({ TableName: 'MyTable', Limit: 5, ExclusiveStartKey: { id: '123' } })

What is the most likely cause?

medium

A. ExclusiveStartKey is missing required key attributes.

B. Limit cannot be used with ExclusiveStartKey.

C. TableName is incorrect.

D. Limit value must be greater than 10.

Solution

1. Step 1: Understand ExclusiveStartKey requirements

   ExclusiveStartKey must include the full primary key attributes exactly as stored in the table.

2. Step 2: Identify error cause

   If the provided ExclusiveStartKey lacks required key attributes or has wrong format, DynamoDB returns an error.

3. Final Answer:

   ExclusiveStartKey is missing required key attributes. -> Option A

4. Quick Check:

   ExclusiveStartKey needs full primary key [OK]

Hint: ExclusiveStartKey must have full primary key attributes [OK]

Common Mistakes:

• Thinking Limit and ExclusiveStartKey cannot be combined
• Assuming TableName typo causes this error
• Believing Limit must be > 10

5. You want to fetch all items from a large DynamoDB table but only 4 items at a time to avoid timeouts. Which approach correctly implements pagination?

hard

A. Use Limit: 4 and pass LastEvaluatedKey from previous response as ExclusiveStartKey in next query.

B. Use Limit: 4 and always start query with ExclusiveStartKey: null.

C. Use Limit: 4 and increase Limit by 4 each time to get next items.

D. Use Limit: 4 and scan the whole table once without ExclusiveStartKey.

Solution

1. Step 1: Understand pagination with Limit and ExclusiveStartKey

   Limit controls how many items are returned per request. To get next items, use ExclusiveStartKey with LastEvaluatedKey from previous response.

2. Step 2: Confirm correct pagination process

   Use Limit: 4 and pass LastEvaluatedKey from previous response as ExclusiveStartKey in next query to fetch items in pages. Restarting from the beginning, increasing Limit, or scanning without pagination leads to repeated or incomplete results.

3. Final Answer:

   Use Limit: 4 and pass LastEvaluatedKey from previous response as ExclusiveStartKey in next query. -> Option A

4. Quick Check:

   Pagination = Limit + ExclusiveStartKey chaining [OK]

Hint: Pass LastEvaluatedKey as ExclusiveStartKey to paginate [OK]

Common Mistakes:

• Restarting query without ExclusiveStartKey
• Increasing Limit instead of paginating
• Scanning whole table ignoring pagination