Partition key distribution in DynamoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a partition key in DynamoDB?

A partition key is the attribute DynamoDB uses to distribute data across partitions. It determines where data is stored and how it is accessed.

beginner

Why is good partition key distribution important?

Good partition key distribution ensures data and workload are spread evenly across partitions, preventing hot partitions and improving performance.

intermediate

What happens if many items share the same partition key?

If many items share the same partition key, it creates a hot partition, causing slower performance and throttling because all requests go to one partition.

intermediate

How can you design a partition key to avoid hot partitions?

Use high-cardinality attributes that have many unique values, or add randomness or time-based elements to the key to spread data evenly.

beginner

What is the role of partition key in query performance?

The partition key helps DynamoDB quickly locate the partition storing the data, making queries efficient by targeting only relevant partitions.

What does DynamoDB use the partition key for?

A To sort items within a partition

B To backup data

C To encrypt data

D To distribute data across partitions

The partition key determines how DynamoDB distributes data across partitions.

What is a hot partition?

A A partition that is offline

B A partition with too many requests or data concentrated on one key

C A partition that stores encrypted data

D A partition used for backups

A hot partition happens when many requests target the same partition key, causing performance issues.

Which attribute type is best for a partition key to avoid hot partitions?

A High-cardinality attribute

B Low-cardinality attribute

C Constant value

D Null value

High-cardinality attributes have many unique values, helping spread data evenly.

How does DynamoDB locate data using the partition key?

A By hashing the partition key to find the partition

B By using the sort key only

C By sorting all items

D By scanning all partitions

DynamoDB hashes the partition key to determine the partition where data is stored.

What is a simple way to improve partition key distribution?

A Use the same partition key for all items

B Use a fixed string as partition key

C Add a random or time-based suffix to the partition key

D Avoid using a partition key

Adding randomness or time-based elements helps spread data across partitions.

Explain what a partition key is and why its distribution matters in DynamoDB.

Think about how DynamoDB spreads data and handles requests.

Describe strategies to design a partition key that avoids hot partitions.

Consider how to make keys unique and balanced.

Practice

1. What is the main purpose of a partition key in DynamoDB?

easy

A. To create backups of the database

B. To store large files in the database

C. To encrypt data automatically

D. To divide data into parts for faster access

Solution

1. Step 1: Understand the role of partition key

   The partition key is used to split data into different sections called partitions.

2. Step 2: Recognize the benefit of partitioning

   This splitting helps DynamoDB access data faster by looking in smaller parts instead of the whole table.

3. Final Answer:

   To divide data into parts for faster access -> Option D

4. Quick Check:

   Partition key divides data = faster access [OK]

Hint: Partition key splits data to speed up access [OK]

Common Mistakes:

• Thinking partition key stores files
• Confusing partition key with encryption
• Assuming partition key creates backups

2. Which of the following is the correct way to define a partition key in a DynamoDB table using AWS CLI?

easy

A. aws dynamodb create-table --table-name MyTable --key-schema AttributeName=UserId,KeyType=HASH --attribute-definitions AttributeName=UserId,AttributeType=S --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5

B. aws dynamodb create-table --table-name MyTable --partition-key UserId --attribute-type String

C. aws dynamodb create-table --table-name MyTable --key UserId --type HASH

D. aws dynamodb create-table --table-name MyTable --primary-key UserId STRING

Solution

1. Step 1: Review AWS CLI syntax for creating table with partition key

   The correct syntax uses --key-schema with AttributeName and KeyType=HASH for partition key.

2. Step 2: Check attribute definitions and throughput

   Attribute definitions must specify AttributeName and AttributeType, and provisioned throughput is required.

3. Final Answer:

   aws dynamodb create-table --table-name MyTable --key-schema AttributeName=UserId,KeyType=HASH --attribute-definitions AttributeName=UserId,AttributeType=S --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5 -> Option A

4. Quick Check:

   Correct AWS CLI syntax = aws dynamodb create-table --table-name MyTable --key-schema AttributeName=UserId,KeyType=HASH --attribute-definitions AttributeName=UserId,AttributeType=S --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5 [OK]

Hint: Use --key-schema with KeyType=HASH for partition key [OK]

Common Mistakes:

• Using --partition-key instead of --key-schema
• Missing attribute definitions
• Incorrect key type syntax

3. Given a DynamoDB table with partition key 'UserId' having only two values: 'A' and 'B', what is the likely impact on partition key distribution?

medium

A. Good distribution because two keys are enough

B. Poor distribution causing hot partitions

C. No impact because DynamoDB balances automatically

D. Table will reject writes due to low key variety

Solution

1. Step 1: Understand partition key uniqueness importance

   Partition keys with few unique values cause data to cluster in few partitions.

2. Step 2: Recognize effect of low unique keys

   This clustering leads to hot partitions, slowing down performance and limiting scalability.

3. Final Answer:

   Poor distribution causing hot partitions -> Option B

4. Quick Check:

   Few unique keys = hot partitions [OK]

Hint: Few keys cause hot partitions, hurting performance [OK]

Common Mistakes:

• Assuming two keys are enough for good distribution
• Believing DynamoDB auto-balances all cases
• Thinking table rejects writes for low key variety

4. You notice your DynamoDB table has uneven partition key distribution causing slow queries. Which change will fix this?

medium

A. Change partition key to a field with many unique values

B. Increase read capacity units only

C. Add a sort key with the same values as partition key

D. Delete and recreate the table without changes

Solution

1. Step 1: Identify cause of uneven distribution

   Uneven distribution happens when partition key has few unique values.

2. Step 2: Choose a partition key with high uniqueness

   Changing to a key with many unique values spreads data evenly across partitions, improving performance.

3. Final Answer:

   Change partition key to a field with many unique values -> Option A

4. Quick Check:

   High uniqueness partition key = even distribution [OK]

Hint: Pick partition key with many unique values to fix distribution [OK]

Common Mistakes:

• Only increasing capacity without fixing key
• Adding sort key with same values doesn't help
• Recreating table without changing key

5. You have a DynamoDB table storing orders with partition key 'CustomerId'. Some customers place thousands of orders daily, others only a few. How can you improve partition key distribution to avoid hot partitions?

hard

A. Use 'OrderId' alone as partition key

B. Keep 'CustomerId' as partition key and add 'OrderId' as sort key

C. Use a composite key combining 'CustomerId' and 'OrderDate' as partition key

D. Use a random number as partition key for all orders

Solution

1. Step 1: Identify problem with current partition key

   Using only 'CustomerId' causes hot partitions for customers with many orders.

2. Step 2: Improve distribution by combining keys

   Combining 'CustomerId' and 'OrderDate' creates more unique partition keys, spreading load better.

3. Step 3: Understand why other options fail

   Keep 'CustomerId' as partition key and add 'OrderId' as sort key keeps same partition key, so hot partitions remain; Use 'OrderId' alone as partition key loses customer grouping; Use a random number as partition key for all orders breaks data organization.

4. Final Answer:

   Use a composite key combining 'CustomerId' and 'OrderDate' as partition key -> Option C

5. Quick Check:

   Composite key increases uniqueness, reduces hot partitions [OK]

Hint: Combine keys to increase uniqueness and spread load [OK]

Common Mistakes:

• Adding sort key but not changing partition key
• Using only order ID loses customer grouping
• Random keys break data access patterns