A fleet telematics platform for a global shipping company tracks container location, internal temperature, and humidity sensors. The telemetry data ingestion service writes updates to an Amazon RDS for PostgreSQL DB instance. A fleet dashboard application frequently queries the database to retrieve the latest state configurations for thousands of active containers. During shift handovers, query volume to retrieve container state configurations spikes dramatically, causing the RDS DB instance to reach 98% CPU utilization and leading to timeout errors in the dashboard. The container state configuration data is highly repetitive, must survive cache node restarts, and requires high availability with sub-millisecond read latency and automatic failover across multiple Availability Zones. Which of the following database and caching strategies should a Solutions Architect implement to resolve the performance bottleneck while meeting the availability and latency requirements?
- AConfigure the Amazon RDS for PostgreSQL DB instance to use a Multi-AZ deployment. Modify the dashboard application's read database connection strings to target the secondary standby DB instance's endpoint during query spikes, offloading the primary DB instance.
- BDeploy an Amazon ElastiCache for Memcached cluster with nodes distributed across multiple Availability Zones. Configure the dashboard application to use client-side hashing to partition the container state configuration data across the nodes, and enable automatic multi-AZ replication to ensure the configuration data survives node failures.
- Deploy an Amazon ElastiCache for Redis replication group with Multi-AZ and automatic failover enabled. Modify the dashboard application to use a cache-aside pattern to read container configurations from ElastiCache, falling back to the PostgreSQL database on cache misses and writing updates to the cache when the database is updated.Cevap
- DSet up a pilot light disaster recovery database environment in a secondary AWS Region with a smaller instance class using cross-region replication. During peak shift handovers, configure the dashboard application to route all container state queries to the secondary region's database to offload the primary database.