Common Single-Table design modeling mistakes with DynamoDB 

The best explanation of the design concept. I can see you must have spent a lot of time and effort to produce such a coherent presentation.

Gained lots from this video. I have been watching RU-vid videos for DynamoDB. Your method of 'Show and Why' went that little bit further of 'Show and Do This Way'. Your explanations help me understand why things are done as best practices.

This is a GEM.

this is a really great explanation, thanks for taking the time to put it together!

Tyler is gonna be a leader in this space within the next decade, hear him out!

Thanks Tyler, great talk

Interesting way to look at design

Great explanation!! Do you have plans to make some videos on ElectroDB? especially advanced concepts.

This was excellent. Thank you Tyler. It's too bad you don't offer modeling services as a freelancer.

Thank you!

Great presentation. Practical callouts and commentary added so much to these otherwise familiar concepts.

How would I get all courses that are in building01 and building02 etc

This is all very cool. But seems like a lot of contortions and conventions to make up for the absence of things that something like mongo does out of the box with indexes, $lookup, ...

I have a controversy about this design. There is too much duplication. It forces the use of a unique name. It doesn't allow to use of non-uniq names I prefer to use ulid. It keeps unique and ordered. ulid ID has date in ID, ulid keeps an ordering