Read traffic to an RDS database has increased.
Keep the writer while distributing read queries to several database instances.
Which method is most appropriate?
RDS read replicas use asynchronous replication to scale read traffic; a Multi-AZ standby is primarily for availability and failover.
Detailed explanation
A snapshot is recovery data, not a running database that processes queries.
A snapshot is recovery data, not a running database that processes queries.
The Multi-AZ standby is for high availability and failover, not a normal read endpoint.
The Multi-AZ standby is for high availability and failover, not a normal read endpoint.
Read replicas distribute read-only processing through asynchronous replication.
Read replicas distribute read-only processing through asynchronous replication.
Application-local memory is not a shared or durable database read-scaling method.
Application-local memory is not a shared or durable database read-scaling method.
Check official documentation
Compare the following points with the official documentation.
Amazon RDSのリードレプリカとMulti-AZの公式説明を確認する。
What to confirm
読み取りスケールにはリードレプリカを選び、Multi-AZとの用途を区別できる。
Key points
- RDS read replica
- Read scaling
- Asynchronous replication
- Multi-AZ
Notes
- Environment: AWS公式RDSドキュメントの確認
- Confirm current AWS architecture guidance and service behavior in the official documentation.
Foundation review
Read versus failover
Read replicas serve queries; Multi-AZ protects availability and failover.
Consistency trade-off
Asynchronous replicas can lag, so applications should use them with that behavior in mind.