- Newest
- Most votes
- Most comments
Hi - It depends on the database type (assuming this is for nosql) and overall access pattern. Also assuming this is for DynamoDB, you may want to review best practices and data modeling techniques based on end to end requirements.
- Best practices for designing and architecting with DynamoDB
- AWS re:Invent 2021 - Data modeling with Amazon DynamoDB
You may also think about selecting the right partition key like https://aws.amazon.com/blogs/database/choosing-the-right-dynamodb-partition-key/ and also indexes https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/SecondaryIndexes.html
What you have a basic structure is fine assuming that these reviews can be replaced or may be cumulative in nature meaning user_id: 'AAAA' may provide a new review for name: 'Bobs Farm' with a new review_id or same and hence the history may co-exist or replaced. But you have to pull only latest . So think on all partition keys and indexes. See process here https://docs.aws.amazon.com/prescriptive-guidance/latest/dynamodb-data-modeling/step3.html
Relevant content
- asked 8 months ago
- asked 2 years ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago