Why single-table design matters in DynamoDB - See It in Action

Why Single-Table Design Matters in DynamoDB

📖 Scenario: You are building a simple online store database using DynamoDB. You want to store information about products and orders efficiently.

🎯 Goal: Build a single DynamoDB table that holds both product and order data using a single-table design approach.

📋 What You'll Learn

Create a DynamoDB table named Store with a partition key PK and sort key SK.

Add two items: one product item and one order item, each with distinct PK and SK values.

Use a Type attribute to distinguish between product and order items.

Add an attribute Price for the product and Quantity for the order.

💡 Why This Matters

🌍 Real World

Single-table design is used in real-world DynamoDB applications to store related data in one table for faster queries and simpler management.

💼 Career

Understanding single-table design is important for roles working with AWS DynamoDB, backend development, and cloud database architecture.

1

Create the DynamoDB table structure

Create a DynamoDB table named Store with a partition key called PK and a sort key called SK.

DynamoDB

# Your code here to define the table with PK and SK

Need a hint?

Define the table with PK as the partition key and SK as the sort key.

2

Add a product item

Add an item to the Store table with PK set to PRODUCT#1001, SK set to METADATA, Type set to Product, and Price set to 29.99.

DynamoDB

TableName: Store
KeySchema:
  - AttributeName: PK
    KeyType: HASH
  - AttributeName: SK
    KeyType: RANGE
AttributeDefinitions:
  - AttributeName: PK
    AttributeType: S
  - AttributeName: SK
    AttributeType: S
BillingMode: PAY_PER_REQUEST

# Add a product item with PK 'PRODUCT#1001', SK 'METADATA', Type 'Product', and Price 29.99
# Your code here

Need a hint?

Use PK and SK to uniquely identify the product item and add Type and Price attributes.

3

Add an order item

Add an item to the Store table with PK set to ORDER#5001, SK set to METADATA, Type set to Order, and Quantity set to 3.

DynamoDB

TableName: Store
KeySchema:
  - AttributeName: PK
    KeyType: HASH
  - AttributeName: SK
    KeyType: RANGE
AttributeDefinitions:
  - AttributeName: PK
    AttributeType: S
  - AttributeName: SK
    AttributeType: S
BillingMode: PAY_PER_REQUEST

Items:
  - PK: PRODUCT#1001
    SK: METADATA
    Type: Product
    Price: 29.99

# Add an order item with PK 'ORDER#5001', SK 'METADATA', Type 'Order', and Quantity 3
# Your code here

Need a hint?

Use PK and SK to uniquely identify the order item and add Type and Quantity attributes.

4

Explain why single-table design matters

Add a comment explaining why using a single table with PK and SK to store different item types like products and orders is beneficial in DynamoDB.

DynamoDB

TableName: Store
KeySchema:
  - AttributeName: PK
    KeyType: HASH
  - AttributeName: SK
    KeyType: RANGE
AttributeDefinitions:
  - AttributeName: PK
    AttributeType: S
  - AttributeName: SK
    AttributeType: S
BillingMode: PAY_PER_REQUEST

Items:
  - PK: PRODUCT#1001
    SK: METADATA
    Type: Product
    Price: 29.99
  - PK: ORDER#5001
    SK: METADATA
    Type: Order
    Quantity: 3

# Add a comment explaining the benefit of single-table design
# Your code here

Need a hint?

Explain in a comment how single-table design helps with efficiency and simplicity.