Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

Single-table sketch

This revision card explains Single-table sketch. It starts from the need that one ER table per entity fights DynamoDB query shapes. It describes many entity types in one table with USER# / ORD# prefixes and overloaded SK. The how-to section notes entity list , then PK/SK matrix , then adjacency edges , then prove with Query. An example on the card is carlos Rivera sketches CartLite keys on a whiteboard before CDK.

Single-table sketch One ER table per entity fights DynamoDB query shapes. Many entity types in one table with USER# / ORD# prefixes and overloaded SK. Entity list → PK/SK matrix → adjacency edges → prove with Query. Carlos Rivera sketches CartLite keys on a whiteboard before CDK.
Single-table sketch · Download PNG
Read card text

What this card says

Why do we need it?

One ER table per entity fights DynamoDB query shapes.

What is it?

Many entity types in one table with USER# / ORD# prefixes and overloaded SK.

single-table

How to do it

Entity list → PK/SK matrix → adjacency edges → prove with Query.

Example

Carlos Rivera sketches CartLite keys on a whiteboard before CDK.

See all AWS revision cards