Introducing Read Replicas

Introduction

In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. To expand the DB instance read ability to offload read pressure on the database, you can create read replicas in a region. These read replicas can process a large number of read requests and increase application throughput.

A read replica uses the architecture of a single physical node (without a slave node). Changes to the primary DB instance are also automatically synchronized to all associated read replicas through the native replication function of MySQL. The synchronization is not affected by network latency. Read replicas and the primary DB instance must be in the same region but can be in different AZs.

Functions

Specifications of read replicas can be different from those of the primary DB instance, and can be changed at any time.
You do not need to maintain accounts or databases. Both of them are synchronized from the primary DB instance.
Read replicas support system performance monitoring.
RDS provides up to 20 monitoring metrics, including storage space, IOPS, number of database connections, CPU usage, and network traffic. You can view these metrics to understand the load of DB instances.

Constraints

A maximum of five read replicas can be created for a primary DB instance.
Read replicas do not support backup settings or temporary backups.
Read replicas do not support restoration from backups.
Data cannot be migrated to read replicas.
Read replicas do not support database creation and deletion.
Read replicas do not support account creation. You can create accounts only on primary DB instances.