Sort key purpose and usage in DynamoDB - Step-by-Step Execution

Concept Flow - Sort key purpose and usage

Start: Table with Partition Key

↓

Add Sort Key to Table

↓

Partition Key groups items

↓

Sort Key orders items within group

↓

Query by Partition Key + Sort Key range

↓

Retrieve ordered subset of items

The sort key organizes items within each partition key group, enabling ordered queries and efficient data retrieval.

Execution Sample

DynamoDB

PartitionKey = 'User#123'
SortKey = 'Order#001'
Query: PartitionKey = 'User#123' AND SortKey BETWEEN 'Order#001' AND 'Order#005'

This query fetches orders for User#123 sorted by order number from 001 to 005.

Execution Table

Step	Action	Partition Key	Sort Key Condition	Resulting Items
1	Start query	User#123	None	All items with PartitionKey 'User#123'
2	Apply Sort Key filter	User#123	SortKey BETWEEN 'Order#001' AND 'Order#005'	Items with SortKey Order#001 to Order#005
3	Return results	User#123	SortKey BETWEEN 'Order#001' AND 'Order#005'	Ordered list of 5 orders
4	End	User#123	SortKey BETWEEN 'Order#001' AND 'Order#005'	Query complete

💡 Query ends after retrieving all items matching PartitionKey and SortKey range.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
PartitionKey	None	User#123	User#123	User#123	User#123
SortKey Condition	None	None	BETWEEN 'Order#001' AND 'Order#005'	BETWEEN 'Order#001' AND 'Order#005'	BETWEEN 'Order#001' AND 'Order#005'
Resulting Items	None	All User#123 items	Filtered to Order#001 to Order#005	Ordered 5 items	Returned 5 items

Key Moments - 2 Insights

Why do we need a sort key if we already have a partition key?

The partition key groups items, but the sort key orders items within that group. Without a sort key, items in the same partition are unordered, making range queries or ordered retrieval impossible. See execution_table step 2 where the sort key filter narrows results.

Can we query only by sort key without partition key?

No, DynamoDB requires the partition key to locate the data partition first. The sort key only works to order or filter items within that partition. This is shown in execution_table step 1 where the partition key is mandatory.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Partition Key value used at step 2?

A Order#001

B Order#005

C User#123

D None

💡 Hint

Check the Partition Key column at step 2 in the execution_table.

At which step does the query apply the Sort Key filter?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the Action column in execution_table to find when the Sort Key condition is applied.

If we remove the Sort Key condition, how would the Resulting Items change at step 2?

A Only one item would be returned

B All items with PartitionKey 'User#123' would be returned

C No items would be returned

D Items from other partitions would be included

💡 Hint

Refer to execution_table step 1 and 2 Resulting Items column to compare.

Concept Snapshot

Sort key organizes items within the same partition key.
It enables ordered queries and range filtering.
Partition key locates the group; sort key orders inside it.
Queries need partition key; sort key refines results.
Use sort key for efficient data retrieval and sorting.

Full Transcript

In DynamoDB, the sort key is used together with the partition key to organize data. The partition key groups items into partitions, and the sort key orders items within each partition. When querying, you must specify the partition key to find the right group. Then you can use the sort key to filter or order items, like getting orders between certain numbers for a user. This makes queries efficient and results ordered. The execution table shows how a query starts with the partition key, applies the sort key filter, and returns ordered results. Beginners often wonder why the sort key is needed or if it can be used alone. The sort key cannot be used without the partition key because DynamoDB needs to find the partition first. Removing the sort key condition returns all items in the partition. Understanding this helps write better queries and design tables well.