Soru

Zorluk: KolayHigh-Performing Database Solutions

An application developer is launching a new multiplayer gaming platform. The game must store player session states with single-digit millisecond read and write latency. The traffic is highly volatile and fluctuates throughout the day, experiencing sudden spikes during weekend tournaments. Which database configuration should a solutions architect recommend to support this workload while minimizing management overhead?

  1. A
    Amazon DynamoDB configured with provisioned capacity mode and a monotonically increasing partition key such as login timestamp
  2. Amazon DynamoDB configured with on-demand capacity mode and a high-cardinality partition key such as user IDCevap
  3. C
    Amazon RDS PostgreSQL DB instance with multiple Read Replicas configured to promote a replica to primary during write spikes
  4. D
    Amazon DynamoDB configured with provisioned capacity mode and a static write capacity unit setting matched to average daily traffic

Cevap

Amazon DynamoDB configured with on-demand capacity mode and a high-cardinality partition key such as user ID
Amazon DynamoDB configured with on-demand capacity mode is ideal for workloads that are highly unpredictable and spiky, as it automatically scales read and write capacity in response to traffic. Using a high-cardinality partition key like user ID ensures that traffic is distributed evenly across multiple partitions, avoiding hot partitions and maintaining single-digit millisecond latency.

Adım Adım Çözüm

1
Analyze application requirements for latency and traffic patterns.
The application requires single-digit millisecond read/write latency with highly volatile and spiky traffic patterns.
This helps determine the database type (NoSQL/DynamoDB for single-digit millisecond performance) and the capacity scaling strategy.
2
Select the appropriate capacity mode for the unpredictable workload.
Amazon DynamoDB with on-demand capacity mode is chosen.
On-demand mode scales instantly to handle sudden spikes without manual intervention or risk of throttling.
3
Choose a partition key design to prevent performance bottlenecks.
A high-cardinality partition key like user ID is selected.
High-cardinality keys distribute read and write operations uniformly across partitions, avoiding performance-limiting hot partitions.

Anahtar Kavram

Designing high-performing, scalable NoSQL databases with Amazon DynamoDB by choosing the appropriate capacity mode and avoiding hot partition keys.
Bu soruyu puanla