Chapter 11: Strategies for one-to-many relationships

A one-to-many relationship is when a particular object is the owner or source for a number of sub-objects. For example, Workplace: A single office will have many employees working there; a single manager may have many direct reports. With one-to-many relationships, there’s one core problem: how do I fetch information about the parent entity when retrieving one or more of the related entities?

In this chapter, we will cover five strategies for modeling one-to- many relationships with DynamoDB:

1: Denormalization by using a complex attribute

2: Denormalization by duplicating data

3: Composite primary key + the Query API action

4: Secondary index + the Query API action

5: Composite sort keys with hierarchical data