Data Modelling Patterns

Data modelling in DynamoDB is fundamentally different from relational databases. Instead of normalising data and using joins, you denormalise and design your table around your access patterns. This lesson covers the key modelling strategies.

---

The DynamoDB Design Process

In a relational database, you design the schema first and then write queries. In DynamoDB, you reverse the process:

1. List your access patterns — every query your application needs
2. Design your primary key and indexes to support those patterns
3. Model your data to fit the key design

Relational:  Schema → Queries
DynamoDB:    Access Patterns → Key Design → Schema

---

Single-Table Design

Single-table design is the most powerful DynamoDB modelling technique. Instead of creating separate tables for each entity, you store all entities in a single table using structured partition and sort keys.

Why Single Table?

Benefit	Description
Fewer round trips	Fetch related data in a single Query
Simpler operations	One table to manage, backup, and monitor
Transaction scope	Transactions work across items in the same table
Reduced costs	Fewer tables, fewer indexes