Scan vs query performance in AWS - Performance Comparison

Time Complexity: Scan vs query performance

O(n)

Understanding Time Complexity

When working with AWS databases, it is important to know how fast different data retrieval methods work as data grows.

We want to understand how the time to get data changes when using scan versus query operations.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

# Query operation
aws dynamodb query --table-name MyTable --key-condition-expression "UserId = :userId" --expression-attribute-values '{":userId":{"S":"123"}}'

# Scan operation
aws dynamodb scan --table-name MyTable
    

The query fetches items matching a specific key, while the scan reads all items in the table.

Identify Repeating Operations

• Primary operation: Reading items from the database.
• How many times: Query reads only matching items; Scan reads every item in the table.

How Execution Grows With Input

As the number of items in the table grows, query reads only a small subset, but scan reads all items.

Input Size (n)	Approx. Api Calls/Operations
10	Query: few calls; Scan: 10 calls
100	Query: few calls; Scan: 100 calls
1000	Query: few calls; Scan: 1000 calls

Pattern observation: Query time stays mostly the same; Scan time grows directly with table size.

Final Time Complexity

Time Complexity: O(n) for scan, O(1) for query

This means scan time grows with the number of items, but query time stays mostly constant for targeted lookups.

Common Mistake

[X] Wrong: "Scan and query take the same time because they both read data from the table."

[OK] Correct: Scan reads every item, so time grows with table size. Query reads only matching items, so time stays small.

Interview Connect

Understanding how scan and query scale helps you design efficient data access in cloud apps, a key skill for real projects.

Self-Check

"What if we added an index to the table? How would that affect the time complexity of queries and scans?"

Practice

1. Which AWS DynamoDB operation is faster when you know the exact primary key of the item you want to retrieve?

easy

A. Update

B. Scan

C. Query

D. Delete

Solution

1. Step 1: Understand Query operation

   Query retrieves items by specifying the primary key, making it fast and efficient.

2. Step 2: Compare with Scan operation

   Scan reads the entire table, which is slower and more costly when you know the key.

3. Final Answer:

   Query -> Option C

4. Quick Check:

   Known key = Query [OK]

Hint: Use Query for known keys, Scan reads all data [OK]

Common Mistakes:

• Thinking Scan is faster for known keys
• Confusing Update or Delete with data retrieval
• Assuming Query reads the whole table

2. Which of the following is the correct syntax to perform a Query operation in AWS DynamoDB using the AWS CLI?

easy

A. aws dynamodb query --table-name MyTable --key-condition-expression 'Id = :id' --expression-attribute-values '{":id":{"S":"123"}}'

B. aws dynamodb scan --table-name MyTable --key-condition-expression 'Id = :id' --expression-attribute-values '{":id":{"S":"123"}}'

C. aws dynamodb get-item --table-name MyTable --key '{"Id":{"S":"123"}}'

D. aws dynamodb update-item --table-name MyTable --key '{"Id":{"S":"123"}}'

Solution

1. Step 1: Identify Query command syntax

   The Query operation uses 'aws dynamodb query' with key-condition-expression and expression-attribute-values.

2. Step 2: Check other options

   Scan reads the entire table (and does not support --key-condition-expression), get-item retrieves a single item by exact key, update-item modifies items, so only the Query syntax is correct.

3. Final Answer:

   aws dynamodb query --table-name MyTable --key-condition-expression 'Id = :id' --expression-attribute-values '{":id":{"S":"123"}}' -> Option A

4. Quick Check:

   Query syntax uses 'query' command [OK]

Hint: Query uses 'aws dynamodb query' command [OK]

Common Mistakes:

• Using Scan command instead of Query
• Confusing GetItem with Query
• Incorrect expression-attribute-values format

3. Given a DynamoDB table with 1000 items, what will be the main difference in performance between these two operations?

1. Query with KeyConditionExpression on partition key
2. Scan without any filter

medium

A. Both read the same number of items and have similar speed

B. Scan reads fewer items and is faster; Query reads all items and is slower

C. Both read all items but Query is slower due to filtering

D. Query reads fewer items and is faster; Scan reads all items and is slower

Solution

1. Step 1: Analyze Query operation

   Query uses the partition key to directly find matching items, reading fewer items and faster.

2. Step 2: Analyze Scan operation

   Scan reads every item in the table, making it slower and more expensive.

3. Final Answer:

   Query reads fewer items and is faster; Scan reads all items and is slower -> Option D

4. Quick Check:

   Query = fewer reads, Scan = full table [OK]

Hint: Query targets keys, Scan reads whole table [OK]

Common Mistakes:

• Assuming Scan is faster than Query
• Thinking Query reads all items
• Ignoring cost differences

4. You wrote this DynamoDB Scan command but it is very slow:

aws dynamodb scan --table-name Users

What is the best way to improve performance if you only want users with UserId = '123'?

medium

A. Replace Scan with Query using KeyConditionExpression on UserId

B. Add a FilterExpression to the Scan command

C. Increase the Read Capacity Units of the table

D. Use UpdateItem to modify the UserId

Solution

1. Step 1: Identify problem with Scan

   Scan reads all items, causing slowness when filtering after reading.

2. Step 2: Use Query for known key

   Query with KeyConditionExpression on UserId reads only matching items, improving speed.

3. Final Answer:

   Replace Scan with Query using KeyConditionExpression on UserId -> Option A

4. Quick Check:

   Known key = Query, not Scan [OK]

Hint: Use Query with key condition, not Scan with filter [OK]

Common Mistakes:

• Adding filter to Scan instead of using Query
• Increasing capacity without optimizing query
• Using UpdateItem unrelated to read performance

5. You have a DynamoDB table with 1 million items. You need to retrieve all items where the attribute 'Status' equals 'Active'. The table's primary key is 'UserId'. Which approach gives the best performance and cost efficiency?

hard

A. Use Scan with FilterExpression 'Status = Active' to get all matching items

B. Create a Global Secondary Index (GSI) on 'Status' and use Query on the GSI

C. Use Query on the primary key 'UserId' with FilterExpression 'Status = Active'

D. Use Scan without any filter and filter results in your application code

Solution

1. Step 1: Understand Scan with filter

   Scan reads all 1 million items, filtering after reading, which is slow and costly.

2. Step 2: Use GSI for efficient querying

   Creating a GSI on 'Status' allows Query to directly find 'Active' items efficiently.

3. Step 3: Evaluate other options

   Query on primary key can't filter by 'Status' efficiently; scanning without filter wastes resources.

4. Final Answer:

   Create a Global Secondary Index (GSI) on 'Status' and use Query on the GSI -> Option B

5. Quick Check:

   GSI + Query = best performance for non-key attribute [OK]

Hint: Use GSI and Query for non-key attribute filtering [OK]

Common Mistakes:

• Using Scan with filter on large tables
• Querying primary key with filter instead of GSI
• Filtering in application after full Scan