Using Reader Instance in Aurora MYSQL

Question

With the creation of a reading instance, a part of the load of SELECT queries goes to the reading instance. correct?
But for example, let's assume that I put a reading instance of lesser capacity and this one is already with a high processing, when more readings arrive they will always go to that instance or the bank can take advantage of an idleness of the recording instance and forward some things for her?

Accepted Answer

You need to specifically target the reader instance with your application. Any query routing would need to happen in the app as well.

Check out this doc page for more details: [Replication with Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Replication.html)

Answer

Take a look at [Amazon Aurora connection management](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Overview.Endpoints.html#Aurora.Endpoints.Reader).

You control where SELECTS are sent by connecting to an endpoint, Cluster, Reader, Instance, or Custom.

Using Reader Instance in Aurora MYSQL

Contenido relevante