Examkin

Soru

Zorluk: ZorOptimizing Performance with Caching and DAX

A logistics tracking application uses Amazon DynamoDB to store delivery status updates. During peak hours, the application frequently experiences read throttling ("ProvisionedThroughputExceededException") when querying the status of specific high-priority shipments, which are read repeatedly by multiple warehouse terminals using eventually consistent reads. The development team needs to implement a caching solution to reduce the load on the DynamoDB table and minimize tail latency while requiring minimal modifications to the existing application code. Which solution should the development team implement to meet these requirements?

  1. Deploy an Amazon DynamoDB Accelerator (DAX) cluster and update the application code to use the DAX SDK client instead of the standard DynamoDB client.Cevap
  2. B
    Increase the table's provisioned Read Capacity Units (RCUs) and configure DynamoDB Auto Scaling to dynamically scale read capacity based on the spike in traffic.
  3. C
    Deploy an Amazon ElastiCache for Memcached cluster, and modify the application to perform a DynamoDB Scan operation with a FilterExpression to find the item on a cache miss, then populate the cache.
  4. D
    Create an Amazon ElastiCache for Redis cluster, and update the backend Lambda function to establish a new Redis client connection on every single invocation to retrieve the item status.

Cevap

Deploy an Amazon DynamoDB Accelerator (DAX) cluster and update the application code to use the DAX SDK client instead of the standard DynamoDB client.
Deploying an Amazon DynamoDB Accelerator (DAX) cluster and updating the application code to use the DAX SDK client is the optimal solution. DAX provides a fully managed, API-compatible, in-memory cache for DynamoDB. Because the reads are eventually consistent, DAX caches and serves them directly from the item cache, eliminating hot partition read throttling on the underlying DynamoDB table with minimal changes to application logic.

Adım Adım Çözüm

1
Analyze the root cause of the DynamoDB throttling ("ProvisionedThroughputExceededException").
The throttling is caused by repeated reads of specific high-priority shipments (hot partition keys) using eventually consistent reads.
Identifying whether the bottleneck is due to overall capacity constraints or hot partitions determines the correct mitigation strategy.
2
Evaluate the consistency requirement and caching solutions.
Since the read requests are eventually consistent, they are eligible for item caching using either Amazon ElastiCache or Amazon DynamoDB Accelerator (DAX).
Strongly consistent reads bypass the DAX item cache, but eventually consistent reads are served directly from the cache, reducing read load on DynamoDB.
3
Select the caching solution that minimizes code changes and avoids anti-patterns.
Deploying DAX requires only replacing the standard DynamoDB client with the DAX client (API-compatible), whereas ElastiCache requires writing complex custom logic for cache-aside patterns and can lead to inefficient Scan patterns if designed poorly.
DAX is specifically built for DynamoDB caching, offering transparent API integration and automatic cache management without rewriting query logic.

Anahtar Kavram

Using DynamoDB Accelerator (DAX) to resolve read throttling on hot keys with minimal code changes.
Bu soruyu puanla

Konular

Optimizing Performance with Caching and DAX

Bu konudan daha fazla soru