Build with DynamoDB | S1 E4 – Advanced NoSQL Data Modeling with Amazon DynamoDB

This episode continues where the last episode ended, with an example of data modeling for a movie database. You will learn how to model relational data, entities, and relationships in DynamoDB to satisfy various access patterns, and how to make the most of global secondary indexes in DynamoDB. Bring questions!

[ChrisShenton]

This is one of the best DynamoDB modeling walk-throughs I've seen. DAT401 is too advanced and fast, which takes us back to the beginning. There are some interesting patterns and explanations, like using Table PK=SK so that when GSI1 which has PK of Table-PK, we don't get low-cardinality PKs. At 18:11 there's an interesting use of prefix to disclude directors from appearing as part of actors aggregates. Coupling DynamoDB to ElasticsearchService at 27:28 with streams and Lambda was obvious to me -- it's a great solution -- but may not be to everyone.

[sardesaisantosh]

if you had plotted different gsi similar to the base table and shown how typical queries (access patterns) are addressed -- the entire picture would be clear

[ahmadnabil]

How to ensure for example that the actor id actually exists before creating the relation between movie and actors. In other words passing any wrong actor id when creating movie&actor relation will pass and the data invalid, So do I have to check for the existence of the actor id before creating the movie(PK)&actor(SK) item?

[CostaSBD]

Hi, Edin,

Your video was amazing.

I have a question:

What is the best pattern to keep consistency across 1 to N relationship items kept in different partitions?
Ie: If an actor has worked in many movies and we have an item in each of the movies to represent that releationship. How can we keep all that metadata consistent across all the items?

Thanks!

[ahmadnabil]

What if you example the actor name was misspelled how can i make sure updating the actor name in the actor partition will change the actor name in movie partition as well?

[api-first]

If you look at the example that is e. g. shown at 7:53. Would you simply name the PK and SK in a generic way e. g. 'SortID' and 'PartitionUUID'?

[sholland]

Reminiscent of the Six Degrees of Kevin Bacon

[joshuathomas]

What does the "S" in "SNAME" mean?

[josevihanoss]

Edin Zulich...
How does the actual table look like?
How the relationship between the Movie-Actor, Movie-Director items in the table look like?
Does the Movie-Actor relation item have attributes?
I'm stuck at 7:12
Could you help?