Composite sort key pattern in DynamoDB - Step-by-Step Execution

Concept Flow - Composite sort key pattern

Start: Query with Partition Key

↓

Apply Sort Key Filter

↓

Sort Items by Sort Key

↓

Return Filtered and Sorted Results

↓

End

The query starts by selecting items with the same partition key, then filters and sorts them using the composite sort key pattern to organize results.

Execution Sample

DynamoDB

PartitionKey = 'User#123'
SortKey begins_with 'Order#2023#'
Query DynamoDB with these keys

This query fetches all orders for user 123 from 2023 by filtering and sorting on the composite sort key.

Execution Table

Step	Action	Partition Key Filter	Sort Key Condition	Items Matched	Resulting Order
1	Start query	User#123	SortKey begins_with 'Order#2023#'	All items with PartitionKey='User#123'	Unsorted
2	Filter items	User#123	SortKey begins_with 'Order#2023#'	Items: Order#2023#001, Order#2023#002, Order#2023#010	Unsorted
3	Sort items	User#123	SortKey prefix filter applied	Same 3 items	Sorted ascending by SortKey: Order#2023#001, Order#2023#002, Order#2023#010
4	Return results	User#123	SortKey prefix filter applied	3 items	Final sorted list returned

💡 Query ends after returning all items matching partition key and sort key prefix, sorted by sort key.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
PartitionKey	undefined	User#123	User#123	User#123	User#123
SortKey Condition	undefined	begins_with 'Order#2023#'	begins_with 'Order#2023#'	begins_with 'Order#2023#'	begins_with 'Order#2023#'
Matched Items	[]	All with User#123	Filtered to 3 orders	Sorted 3 orders	3 sorted orders

Key Moments - 2 Insights

Why do we need to use a composite sort key instead of just a simple sort key?

Because the composite sort key combines multiple pieces of information (like year and order number) into one string, it allows filtering and sorting on multiple criteria in one step, as shown in execution_table rows 2 and 3.

What happens if the sort key condition is not applied?

Without the sort key condition, the query would return all items with the partition key, unsorted and unfiltered, as shown in execution_table row 1, which can be inefficient and return too many results.

Visual Quiz - 3 Questions

Look at the execution_table, at which step are the items sorted by the composite sort key?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Check the 'Resulting Order' column in execution_table rows.

According to variable_tracker, what is the value of 'Matched Items' after Step 2?

A Filtered to 3 orders

B Empty list []

C All items with PartitionKey 'User#123'

D Sorted 3 orders

💡 Hint

Look at the 'Matched Items' row under 'After Step 2' in variable_tracker.

If the sort key condition was changed to 'begins_with Order#2022#', how would the matched items change?

A They would include orders from 2023

B No items would match

C They would include orders from 2022

D All items with PartitionKey would match

💡 Hint

Refer to how the sort key prefix filters items in execution_table row 2.

Concept Snapshot

Composite sort key pattern in DynamoDB:
- Use PartitionKey to group related items.
- Use composite SortKey combining multiple values (e.g., 'Order#2023#001').
- Query with PartitionKey and SortKey condition (e.g., begins_with).
- DynamoDB returns items filtered and sorted by SortKey.
- Enables efficient queries with multiple criteria in one key.

Full Transcript

The composite sort key pattern in DynamoDB helps organize and query data efficiently. First, you select items by their partition key, which groups related data. Then, you apply a condition on the sort key, which is a combined string of multiple values like year and order number. This filters and sorts the items in one step. The execution table shows how the query starts with all items for a user, filters to those starting with 'Order#2023#', sorts them, and returns the final list. Variables like PartitionKey and SortKey condition remain constant, while matched items change as filtering and sorting happen. Key moments clarify why the composite sort key is useful and what happens if the sort key condition is missing. The quiz tests understanding of sorting step, matched items after filtering, and effects of changing the sort key prefix. The snapshot summarizes the pattern as a way to combine multiple criteria into one key for efficient querying.

Practice

1. What is the main purpose of using a composite sort key in DynamoDB?

easy

A. To create a unique partition key for each item

B. To increase the read capacity of the table

C. To encrypt data stored in the table

D. To combine multiple attributes into one key for better sorting and grouping

Solution

1. Step 1: Understand composite sort key concept

   A composite sort key combines multiple values into one string to organize data efficiently.

2. Step 2: Identify its main use

   This helps group related items and sort them within the same partition key.

3. Final Answer:

   To combine multiple attributes into one key for better sorting and grouping -> Option D

4. Quick Check:

   Composite sort key = combine attributes [OK]

Hint: Composite sort keys combine values to sort and group data [OK]

Common Mistakes:

• Confusing composite sort key with partition key
• Thinking it encrypts data
• Assuming it increases capacity

2. Which of the following is a correct example of a composite sort key format?

easy

A. 2023-04-01_Customer123_Order

B. Customer123|Order|2023-04-01

C. Order:2023-04-01:Customer123

D. Order#2023-04-01#Customer123

Solution

1. Step 1: Identify proper delimiter usage

   Composite sort keys use clear delimiters like colons to separate parts for easy parsing.

2. Step 2: Check each option's delimiter consistency

   Order:2023-04-01:Customer123 uses colons consistently, making it a clear composite key format.

3. Final Answer:

   Order:2023-04-01:Customer123 -> Option C

4. Quick Check:

   Clear delimiters = Order:2023-04-01:Customer123 [OK]

Hint: Use consistent delimiters like ':' in composite keys [OK]

Common Mistakes:

• Using inconsistent or unclear delimiters
• Mixing delimiters without pattern
• Not separating parts clearly

3. Given a DynamoDB table with partition key UserID and composite sort key OrderDate#OrderID, what will be the result of querying for UserID = 'U123' and sort key begins with '2023-05-'?

medium

A. All orders by user U123 placed in May 2023

B. All orders by user U123 regardless of date

C. Orders from all users placed in May 2023

D. No results because sort key format is invalid

Solution

1. Step 1: Understand the composite sort key structure

   The sort key combines OrderDate and OrderID separated by '#', so prefix '2023-05-' matches May 2023 orders.

2. Step 2: Query with partition key and sort key prefix

   Querying UserID='U123' and sort key begins with '2023-05-' returns all U123's orders in May 2023.

3. Final Answer:

   All orders by user U123 placed in May 2023 -> Option A

4. Quick Check:

   Partition + sort key prefix = filtered orders [OK]

Hint: Use sort key prefix to filter by date in composite keys [OK]

Common Mistakes:

• Ignoring partition key in query
• Assuming all users' data is returned
• Misunderstanding sort key prefix filtering

4. You wrote a composite sort key as OrderDate-OrderID but your queries using begins_with('2023-06') return no results. What is the likely problem?

medium

A. The sort key should use a consistent delimiter like ':' or '#' instead of '-'

B. The query must use contains instead of begins_with

C. The delimiter '-' is missing in the query filter

D. The partition key is incorrect

Solution

1. Step 1: Check delimiter consistency in composite keys

   Using '-' as delimiter can cause confusion if date format also contains '-'.

2. Step 2: Understand query prefix matching

   Because date and delimiter both use '-', the prefix '2023-06' may not match correctly; consistent delimiters like ':' or '#' avoid this.

3. Final Answer:

   The sort key should use a consistent delimiter like ':' or '#' instead of '-' -> Option A

4. Quick Check:

   Delimiter confusion breaks prefix queries [OK]

Hint: Avoid delimiters that appear in data parts [OK]

Common Mistakes:

• Using delimiters that clash with data format
• Wrong query function for prefix
• Ignoring partition key correctness

5. You want to design a DynamoDB table to store chat messages with partition key ChatRoomID and composite sort key combining MessageDate and MessageID. Which composite sort key format is best to efficiently query messages by date and maintain uniqueness?

hard

A. MessageID#MessageDate with date in any format

B. MessageDate#MessageID with date in ISO format (YYYY-MM-DDTHH:mm:ss)

C. MessageDate-MessageID with date in MM/DD/YYYY

D. MessageDate_MessageID with date as Unix timestamp

Solution

1. Step 1: Choose delimiter and date format for sorting

   Using '#' as delimiter is clear and ISO date format sorts lexicographically by date/time.

2. Step 2: Ensure uniqueness and query efficiency

   Placing MessageDate first allows range queries by date; MessageID ensures uniqueness within same timestamp.

3. Final Answer:

   MessageDate#MessageID with date in ISO format (YYYY-MM-DDTHH:mm:ss) -> Option B

4. Quick Check:

   ISO date + clear delimiter = best composite key [OK]

Hint: Use ISO date + clear delimiter for sortable composite keys [OK]

Common Mistakes:

• Using ambiguous delimiters
• Placing unique ID before date
• Using non-lexicographically sortable date formats