An online auction portal experiences performance bottlenecks during peak bidding windows. The database tier must support sudden, unpredictable write spikes of up to writes per second, while providing microsecond read latency for retrieving the current highest bid status. The access patterns are simple key-value lookups.
Which combination of database configurations should be implemented to meet these performance and scaling requirements? (Select TWO.)
- Provision an Amazon DynamoDB table and deploy Amazon DynamoDB Accelerator (DAX) to cache read requests.Cevap
- Configure the DynamoDB table with on-demand capacity mode to scale writes automatically in response to sudden traffic spikes.Cevap
- CUse a monotonically increasing partition key, such as the timestamp of the bid, to ensure sequential write distribution across DynamoDB partitions.
- DConfigure an Amazon RDS Multi-AZ database cluster, and route write traffic to an RDS Read Replica if the primary DB instance becomes overloaded.
- EConfigure the DynamoDB table with a low Provisioned Capacity Mode limit to control costs, and rely on application-level retry logic to absorb write spikes.
Cevap
Deploying Amazon DynamoDB with on-demand capacity mode and using Amazon DynamoDB Accelerator (DAX) to cache read requests is the correct solution.
The correct solution involves configuring the database using Amazon DynamoDB with on-demand capacity mode and utilizing Amazon DynamoDB Accelerator (DAX). On-demand capacity mode handles sudden, unpredictable spikes up to writes per second without requiring capacity planning or manual scaling. Amazon DynamoDB Accelerator (DAX) is an in-memory cache specifically built for DynamoDB that reduces read latencies to microseconds, satisfying the performance requirements for retrieving current bid statuses.
Adım Adım Çözüm
Anahtar Kavram
High-performing database architectures utilizing Amazon DynamoDB, on-demand capacity scaling, and DAX caching.