1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
Based on the table design you have described, I don't think it is possible to do it all in 1 table or operation.
However, there are several patterns which you may want to study which may help you reimagine your table design approach for your overall app. Please take a look at the below:
https://aws.amazon.com/blogs/database/single-table-vs-multi-table-design-in-amazon-dynamodb/ https://www.alexdebrie.com/posts/dynamodb-one-to-many/ https://aws.amazon.com/blogs/database/model-hierarchical-automotive-component-data-using-amazon-dynamodb/
I hope this is helpful.
Thanks, Rama
answered 13 days ago
Relevant content
- asked 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you for the fair answer Rama,
Looks like double request is something that is being done in DynamoDB as needed. I found confirmation in how Alex DeBrie describes the fallback for many-to-many relationships modeling in Chapter 12.4 "Normalization and multiple requests" of "The DynamoDB Book" (https://www.dynamodbbook.com).