hardwarehuman
commented
1 year ago Other use cases include being a way to isolate other tasks like DB dumps, serving API requests for data, and other operations away from the DB supplying CRUD operations to the website itself.
pburkholder
Customers are requesting RDS instances to have a read replica so that they that can separately service aggregating analytic queries which might ordinarily cause read locks on tables that block writes during normal site use. Also in general to support RDS instance scaling.
When an RDS instance is provisioned you would then select to also provision a number of read replicas (these would be billed as additional instances). When you bind an application to the RDS instance, you could optionally specify that you are read-only, and you'd get back a different DB URI for a read-replica.
The cost of this feature should be taken into account as it is similar to allowing Multi-AZ it effectively doubles the cost of the primary instance. Possibly link the data usage together as one singular instance?
Discussed in this thread. Linked here is the relevant AWS documentation regarding Read Replicas.
Go SDK documentation on enabling read replicas: https://docs.aws.amazon.com/sdk-for-go/api/service/rds/#RDS.CreateDBInstanceReadReplica
Before implementing this feature, we'll need to determine if it will address the concerns customers have.
cf sshconnectionThere may be other or complementary work for this to address customer needs, such as: