Why Scan reads the entire table in DynamoDB - Visual Breakdown

Concept Flow - Why Scan reads the entire table

Start Scan Operation

↓

Read First Page of Items

↓

Check if More Pages Exist?

No→End Scan

Yes↓

Read Next Page of Items

↩Back to Check

Scan reads all items page by page until no more pages remain, covering the entire table.

Execution Sample

DynamoDB

Scan operation on DynamoDB table
Reads items page by page
Stops when no more pages

This Scan reads every item in the table by paging through all data.

Execution Table

Step	Action	Items Read	More Pages?	Next Step
1	Start Scan	0	Yes	Read first page
2	Read first page	100	Yes	Read next page
3	Read second page	200	Yes	Read next page
4	Read third page	300	No	End Scan
5	End Scan	300	No	Stop

💡 No more pages to read, entire table scanned

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
ItemsRead	0	100	200	300	300
MorePages	Yes	Yes	Yes	No	No

Key Moments - 2 Insights

Why does Scan read all items even if I only want a few?

Scan reads every item page by page until no pages remain, as shown in execution_table rows 2-4, so it always covers the whole table.

What does 'More Pages?' mean in the Scan process?

'More Pages?' indicates if there are more items to read beyond the current page. If Yes, Scan continues reading next pages (rows 2 and 3). If No, Scan ends (row 4).

Visual Quiz - 3 Questions

Look at the execution_table, how many items have been read after step 3?

A 200

B 100

C 300

D 0

💡 Hint

Check the 'Items Read' column at step 3 in execution_table

At which step does the Scan operation stop reading more pages?

A Step 2

B Step 3

C Step 4

D Step 1

💡 Hint

Look at 'More Pages?' column in execution_table where it changes to No

If the table had 500 items and each page reads 100 items, how many steps would the Scan need to finish?

A 4 steps

B 5 steps

C 6 steps

D 3 steps

💡 Hint

Each page reads 100 items, so 500 items means 5 pages to read

Concept Snapshot

Scan reads all items in a DynamoDB table by paging through data.
It reads one page at a time until no more pages remain.
Each page contains a set number of items (e.g., 100).
Scan always covers the entire table, which can be slow for large tables.
Use Query instead to read specific items efficiently.

Full Transcript

The Scan operation in DynamoDB reads the entire table by fetching items page by page. It starts by reading the first page of items, then checks if more pages exist. If yes, it continues reading the next pages until no more pages remain. This means Scan always reads all items in the table, which can be slow for large tables. The execution table shows each step with the number of items read and whether more pages exist. The variable tracker shows how the count of items read increases with each step. Beginners often wonder why Scan reads all items even if only a few are needed; this is because Scan does not filter items before reading. The 'More Pages?' column indicates if the Scan should continue reading. Understanding this flow helps to choose the right operation for efficient data access.