Database Reference
In-Depth Information
• The smaller the index, the cheaper the cost to store it and our write costs will be
cheaper too. If we need to access only those few attributes that have the lowest
possible latency, then we must project only those (lesser) attributes into a global
secondary index.
• If we need to access almost all of the non-key attributes of the DynamoDB table
on a frequent basis, we can project these attributes (even the entire table) into the
global secondary index. This will give us maximum flexibility with the trade-off
that our storage cost would increase, or even double if we project the entire table's
attributes into the index.
• The additional storage costs to store the global secondary index might equalize
the cost of performing frequent table scans. If our application will frequently re-
trieve some non-key attributes, we must consider projecting these non-key attrib-
utes into the global secondary index.
