A Solutions Architect is designing the database architecture for a global corporate travel booking application. The application needs to support high-throughput booking transactions in the primary AWS Region and provide employees worldwide with access to travel history queries with latency under 100 milliseconds. Which of the following database configurations should the Solutions Architect select to meet these performance requirements? (Select TWO.)
- Migrate the database to Amazon Aurora MySQL and configure an Aurora Global Database with read replicas in the secondary Regions to serve local reads.Cevap
- Deploy an Amazon ElastiCache for Redis cluster in each Region to cache frequently read order history data and minimize read latency.Cevap
- CConfigure Amazon RDS for MySQL with cross-Region read replicas, and set up the application to promote the replicas to primary instances during peak write periods to distribute write operations.
- DMigrate the database to an Amazon DynamoDB table using the transaction timestamp as the partition key to ensure sequential sorting and high write performance.
- EMove the order history data to an Amazon DynamoDB table configured in Provisioned Capacity Mode with static read and write capacity units to handle highly unpredictable, spiky traffic.
Cevap
Migrate the database to Amazon Aurora MySQL with an Aurora Global Database configuration and deploy an Amazon ElastiCache for Redis cluster in each Region to cache queries.
Migrating the application database to Amazon Aurora MySQL and using Aurora Global Database enables local read replicas in secondary Regions, which reduces read latency significantly for global users. In addition, deploying Amazon ElastiCache for Redis in each Region caches queries close to the application servers, satisfying the sub-100 millisecond response time requirement.
Adım Adım Çözüm
Anahtar Kavram
Scaling global reads with minimal latency requires a combination of local in-memory caching (Amazon ElastiCache) and fast replication to remote database endpoints (Amazon Aurora Global Database). Schema designs must avoid monotonically increasing keys (like timestamps) to prevent partition hotspots.