Wouldn't it be a better idea to keep Flight _ID as PK and cust_id as sort or sec key. Most of the times as an airline company, I am intrested in finding which flight has the worst review rather than finding which customer gave us the most good review or bad review. An average person will travel and review what 2 0times, compared that to say around 30 - 50 reviews per flight.
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
Should I do these videos where I talk about coaching topics more often?
yes, please :)
yes, it is really helpful ! Thank you so much
This is very useful to get started with dynamo db schema design, looking forward to more in-depth examples.
Wouldn't it be a better idea to keep Flight _ID as PK and cust_id as sort or sec key. Most of the times as an airline company, I am intrested in finding which flight has the worst review rather than finding which customer gave us the most good review or bad review. An average person will travel and review what 2 0times, compared that to say around 30 - 50 reviews per flight.
Don't blindly jump on dynamodb. It has more disadvantages when it comes to listing filtering aggregation pagination.
Thank you for the great explanation Andreas
Thank Andreas, It cleared up my lot of confusion related to Dynamodb. 🙌🙌
1:49 you cannot create a review table if its foreign key is in a table that is not yet created
That's why you would fill the customer table and the flight table first. The order of writing is important
Nice video, can we modify the table after creating on aws?
yes you can modify the tables after creating them
Thank you for useful content. Like the way you use Miro =)
Can you answer a simple question here how to list all customers with multiple filers and my table size is 1TB?
Very helpful thank you!