Hierarchical data modeling in DynamoDB - Mini Project: Build & Apply

Hierarchical Data Modeling in DynamoDB

📖 Scenario: You are building a simple employee directory for a company. Each employee can have a manager, creating a hierarchy. You want to store this data in DynamoDB so you can easily find employees and their managers.

🎯 Goal: Create a DynamoDB table to store employees with their manager relationships using hierarchical data modeling. You will define the table structure, add a configuration for the partition key, insert employee data, and finalize the table setup.

📋 What You'll Learn

Create a DynamoDB table named Employees with EmployeeID as the partition key.

Add a configuration variable for the sort key named ManagerID.

Insert employee items with EmployeeID, Name, and ManagerID attributes.

Complete the table creation with the key schema and attribute definitions.

💡 Why This Matters

🌍 Real World

Companies often need to store employee-manager relationships to manage organizational charts and reporting structures.

💼 Career

Understanding hierarchical data modeling in DynamoDB is useful for roles involving cloud database design, backend development, and data engineering.

1

Create the DynamoDB table with partition key

Write the AWS CLI command to create a DynamoDB table named Employees with EmployeeID as the partition key of type String.

DynamoDB

# aws dynamodb create-table --table-name Employees --attribute-definitions AttributeName=EmployeeID,AttributeType=S --key-schema AttributeName=EmployeeID,KeyType=HASH --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5
# Your code here

Hint

Use the aws dynamodb create-table command with --table-name Employees. Define EmployeeID as the partition key with type String (S).

2

Add sort key configuration for ManagerID

Modify the AWS CLI command to add ManagerID as the sort key of type String in the table creation.

DynamoDB

aws dynamodb create-table --table-name Employees --attribute-definitions AttributeName=EmployeeID,AttributeType=S AttributeName=ManagerID,AttributeType=S --key-schema AttributeName=EmployeeID,KeyType=HASH AttributeName=ManagerID,KeyType=RANGE --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5
# Your code here

Hint

Add ManagerID as a sort key (range key) with type String in both --attribute-definitions and --key-schema.

3

Insert employee items with manager relationships

Write AWS CLI commands to insert two employees: EmployeeID 'E1' named 'Alice' with no manager (empty string), and EmployeeID 'E2' named 'Bob' with manager 'E1'. Use put-item with JSON item data.

DynamoDB

aws dynamodb put-item --table-name Employees --item '{"EmployeeID": {"S": "E1"}, "Name": {"S": "Alice"}, "ManagerID": {"S": ""}}'
aws dynamodb put-item --table-name Employees --item '{"EmployeeID": {"S": "E2"}, "Name": {"S": "Bob"}, "ManagerID": {"S": "E1"}}'
# Your code here

Hint

Use aws dynamodb put-item to add each employee. The ManagerID for Alice is an empty string to indicate no manager.

4

Complete the table setup with key schema and attribute definitions

Ensure the AWS CLI command for creating the Employees table includes both EmployeeID as the partition key and ManagerID as the sort key with correct attribute definitions and key schema.

DynamoDB

aws dynamodb create-table --table-name Employees --attribute-definitions AttributeName=EmployeeID,AttributeType=S AttributeName=ManagerID,AttributeType=S --key-schema AttributeName=EmployeeID,KeyType=HASH AttributeName=ManagerID,KeyType=RANGE --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5
# Your code here

Hint

Double-check the table creation command includes both keys in attribute definitions and key schema.

Practice

1. What is the main purpose of hierarchical data modeling in DynamoDB?

easy

A. To organize data with parent-child relationships

B. To store unrelated data in separate tables

C. To improve data encryption

D. To increase the size of the database

Solution

1. Step 1: Understand hierarchical data modeling

   Hierarchical data modeling organizes data by showing relationships where one item is the parent and others are children.

2. Step 2: Relate to DynamoDB usage

   DynamoDB uses this model to efficiently store and query related items using keys.

3. Final Answer:

   To organize data with parent-child relationships -> Option A

4. Quick Check:

   Hierarchical data = parent-child organization [OK]

Hint: Think parent and child data linked by keys [OK]

Common Mistakes:

• Confusing hierarchical with unrelated data storage
• Thinking it improves encryption
• Assuming it increases database size

2. Which key should be used as the partition key to model a parent item in DynamoDB hierarchical data?

easy

A. Child ID

B. Parent ID

C. Timestamp

D. Random UUID

Solution

1. Step 1: Identify the role of partition key

   The partition key groups related items together in DynamoDB.

2. Step 2: Choose the key representing the parent

   Since the parent is the main group, its ID should be the partition key to link children under it.

3. Final Answer:

   Parent ID -> Option B

4. Quick Check:

   Partition key = Parent ID for grouping [OK]

Hint: Partition key groups parents; use Parent ID [OK]

Common Mistakes:

• Using Child ID as partition key
• Choosing timestamp which is unrelated
• Using random UUID that breaks grouping

3. Given a DynamoDB table with partition key ParentID and sort key ChildID, what will the query KeyConditionExpression: ParentID = 'P1' return?

medium

A. Only child items with ChildID 'P1'

B. Only the parent item with ID 'P1'

C. All items with ParentID 'P1' including parent and children

D. No items, syntax error in query

Solution

1. Step 1: Understand the query condition

   The query filters items where partition key ParentID equals 'P1'.

2. Step 2: Recall hierarchical data structure

   All items with ParentID 'P1' include the parent and its children because they share the same partition key.

3. Final Answer:

   All items with ParentID 'P1' including parent and children -> Option C

4. Quick Check:

   Query by ParentID returns parent + children [OK]

Hint: Query by partition key returns all related items [OK]

Common Mistakes:

• Thinking only parent is returned
• Confusing sort key with partition key
• Assuming syntax error without cause

4. You wrote a DynamoDB query to get all children of a parent using KeyConditionExpression: ParentID = :pid AND ChildID = :cid. It returns only one child instead of all children. What is the mistake?

medium

A. Using '=' on ChildID filters to one child only

B. ParentID should be in filter expression, not key condition

C. Missing a sort key in the table schema

D. ChildID cannot be used in KeyConditionExpression

Solution

1. Step 1: Analyze the key condition

   The condition ChildID = :cid restricts results to one specific child.

2. Step 2: Understand how to get all children

   To get all children, use a range operator like begins_with or omit ChildID condition.

3. Final Answer:

   Using '=' on ChildID filters to one child only -> Option A

4. Quick Check:

   Equals on sort key limits to one item [OK]

Hint: Use range operators, not '=' on sort key for multiple children [OK]

Common Mistakes:

• Thinking ParentID should be filter, not key condition
• Assuming ChildID can't be in key condition
• Ignoring sort key usage in queries

5. You want to model a company hierarchy in DynamoDB where each employee can have multiple subordinates. Which key design best supports efficient queries for all subordinates of a manager?

hard

A. Partition key: EmployeeID, Sort key: Timestamp

B. Partition key: EmployeeID, Sort key: ManagerID

C. Partition key: DepartmentID, Sort key: EmployeeID

D. Partition key: ManagerID, Sort key: EmployeeID

Solution

1. Step 1: Identify parent-child relationship

   Manager is the parent; employees are children (subordinates).

2. Step 2: Choose keys to group subordinates

   Using ManagerID as partition key groups all subordinates under one manager.

3. Step 3: Use EmployeeID as sort key

   Sort key EmployeeID uniquely identifies each subordinate under the manager.

4. Final Answer:

   Partition key: ManagerID, Sort key: EmployeeID -> Option D

5. Quick Check:

   Parent key = ManagerID groups subordinates [OK]

Hint: Partition by parent (manager) to group children (employees) [OK]

Common Mistakes:

• Using EmployeeID as partition key breaks grouping
• Using DepartmentID ignores manager-subordinate relation
• Using timestamp unrelated to hierarchy