Question

A developer built a reporting feature that repeatedly retrieves all orders for a specific customer from a DynamoDB table. The table's partition key is OrderId and it has no secondary indexes. The feature currently uses a Scan operation with a FilterExpression on CustomerId, and users report that the report takes several seconds and consumes a large amount of read capacity as the table grows. What is the most effective way to reduce both latency and read consumption?

Accepted Answer

Create a global secondary index with CustomerId as the partition key and query that index instead of scanning the table.

Answer

Switch the Scan to use eventually consistent reads and increase the page size to retrieve more items per request.

Answer

Enable DynamoDB Accelerator (DAX) so the Scan results are cached and served with microsecond latency.

Answer

Increase the table's provisioned read capacity units so the Scan completes faster under load.