A retail company is launching a new promotions portal that experiences sudden bursts of traffic. The database tier must support two distinct workloads: a transactional relational workload to process orders, and a highly concurrent, low-latency search workload for the active promotions catalog. The solutions architect needs to design a high-performing database architecture that can scale dynamically to handle these demands.
Which combination of database configurations should the solutions architect choose? (Select two.)
- Amazon Aurora MySQL database cluster with Aurora Auto Scaling for read replicas to handle transactional order processingCevap
- Amazon ElastiCache for Redis cluster to cache promotional catalog queriesCevap
- CAmazon DynamoDB table with a partition key of monotonically increasing transaction timestamps to store order details
- DAmazon RDS for MySQL instance using a read replica in a separate Availability Zone as the primary automatic failover mechanism for transaction writes
- EAmazon DynamoDB table configured in Provisioned Capacity Mode with fixed capacity units to handle the highly unpredictable spiky transactional traffic
Cevap
The correct configurations are using an Amazon Aurora MySQL database cluster with Aurora Auto Scaling for read replicas to handle transactional order processing, and deploying an Amazon ElastiCache for Redis cluster to cache promotional catalog queries.
The relational order processing requires a high-performance transactional database, which is served by Amazon Aurora MySQL. Aurora supports Auto Scaling read replicas to handle variable read capacity during traffic spikes. The search catalog requires highly concurrent, low-latency retrieval, which is served by Amazon ElastiCache for Redis, shielding the database from high read volume.
Adım Adım Çözüm
Anahtar Kavram
High-performing database architectures leverage specialized services for different read/write patterns, such as using Aurora MySQL for relational transactional operations and Amazon ElastiCache to cache high-frequency, low-latency read requests.
Tahmini Süre:2m 0s