Fundamentals
Before you model relationships or tune indexes, you need the primitives DynamoDB actually gives you: the value types you can store, how items group on disk, and the key that decides where each item lives. Get these wrong and every later pattern fights you.
Coming from SQL, the surprises start here. There are no columns and no schema — just typed attributes per item — and the primary key isn't a convenience, it's the physical layout of your data.
0 of 9 readQuiz
Start with data types if you're brand new; jump to composite primary keys if you already know the value model and want the part that drives every access pattern.
Want to poke at real items as you read? Try DynoTable and inspect a table's keys and collections directly.