Database Reference
In-Depth Information
An example would be if you want to store blog details in a certain table of DynamoDB,
and the blog body might have more data than the maximum allowed size. Then, we create
one table called blog to store other blog details and one more table to store blog body.
Blog table
The following is how the blog table would look:
Here blog ID could be the hash key blog ID
Blog name
Number of body chunks
1
AWS Best Practices 2
2
DynamoDB Features 2
3
S3 Backup
3
Body chunks table
For the body chunk table, the chunk ID would act as the hash key and could be formed by
appending the chunk number to the blog ID.
Chunk ID
Text
1#1
"…AWS Best Practices 1…"
1#2
"…AWS Best Practices 2…"
2#1
"…DynamoDB Features 1…"
Here, we are storing the blog body in multiple chunks. So, when we get a blog item to be
stored, we first break the body into multiple chunks and then store the data into respective
tables. We can use this batch to get API at the time of retrieval to get the complete body in
one go. Here the chunk ID is formed by combining the parent blog ID and the chunk ID.
Please make a note that this technique is feasible only when your attribute value can be
broken down into chunks. Also, you might need to spend some time on the data splitting
technique, which would also affect the overall time.
