Common Single-Table design modeling mistakes with DynamoDB

Advanced DynamoDB Techniques: Designing your access patterns is hard, designing your keys for scale is even harder! Learn these advanced techniques to modeling your DynamoDB keys before you write records to your database. I have been working with DynamoDB for years and have seen a lot of pitfalls from naively designed keys, in this video I go over every trick I have to model modeling DynamoDB keys with a focus on single-table design.

If you use TypeScript/JavaScript, checkout the library ElectroDB at https://electrodb.dev for a type-safe way to accomplish all of these techniques out of the box!

00:00:00 Introduction
00:00:56 Agenda/Overview
00:01:27 Partition and Sort keys
00:05:48 Single-Table design pros/cons
00:07:32 Our challenge
00:07:55 Presentation conventions
00:08:40 The "Course" entity
00:11:47 Identify natural keys
00:13:06 Separate your attributres from key fields
00:15:28 Standize casing and spacing
00:18:18 Use delimiters after each composite attribute
00:18:58 Why delimiters matter
00:24:29 Zero pad composite attribute numbers
00:26:16 Order composite attribures by hierarchy
00:29:18 Revisit "Course" entity access patterns
00:31:41 The "Certificate" entity
00:31:52 "Certificate" and "Course" entity comparison
00:34:06 Cross entity access patterns
00:39:35 Entity Isolation
00:42:03 Include static prefixes
00:46:23 High Volume of records per partition
00:47:38 High relationship density per partition
00:50:01 Isolating entity versions with keys
00:53:03 Partition key distribution with sharding
01:01:49 Final access patterns
01:05:13 ElectroDB for TypeScript users