Soru

Zorluk: OrtaHigh-Performing Database Solutions

An online auction portal experiences performance bottlenecks during peak bidding windows. The database tier must support sudden, unpredictable write spikes of up to 12,50012,500 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.)

  1. Provision an Amazon DynamoDB table and deploy Amazon DynamoDB Accelerator (DAX) to cache read requests.Cevap
  2. Configure the DynamoDB table with on-demand capacity mode to scale writes automatically in response to sudden traffic spikes.Cevap
  3. C
    Use a monotonically increasing partition key, such as the timestamp of the bid, to ensure sequential write distribution across DynamoDB partitions.
  4. D
    Configure an Amazon RDS Multi-AZ database cluster, and route write traffic to an RDS Read Replica if the primary DB instance becomes overloaded.
  5. E
    Configure 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 12,50012,500 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

1
Analyze the access pattern and latency requirements.
The requirements indicate key-value lookups, microsecond read latency, and millisecond-level write latency. This strongly points to Amazon DynamoDB as the core database service and Amazon DynamoDB Accelerator (DAX) to achieve microsecond read latency.
DynamoDB natively supports high-throughput key-value queries, and DAX provides in-memory caching to reduce read latency from milliseconds to microseconds.
2
Identify the scaling requirement for unpredictable write spikes.
On-demand capacity mode is selected to automatically scale throughput in response to sudden, unpredictable workloads.
Unlike provisioned capacity mode, which requires manual adjustment or auto-scaling policies that may lag behind rapid spikes, on-demand mode instantly accommodates workload changes.
3
Evaluate and eliminate incorrect configuration options.
Monotonically increasing keys, RDS Read Replicas for failover, and low provisioned capacity limits are discarded.
Monotonically increasing keys create hot partitions. RDS Read Replicas cannot serve write traffic or serve as Multi-AZ automatic failover targets. Low provisioned capacity limits cause unacceptable throttling.

Anahtar Kavram

High-performing database architectures utilizing Amazon DynamoDB, on-demand capacity scaling, and DAX caching.
Bu soruyu puanla