Read replicas for performance in AWS - Step-by-Step Execution

Process Flow - Read replicas for performance

Primary Database

↓

Create Read Replica

↓

Replica Syncs Data

↓

Read Traffic Directed to Replica

↓

Primary Handles Writes

↓

Replica Improves Read Performance

The primary database creates a read-only copy called a read replica. The replica syncs data from the primary. Read requests go to the replica, reducing load on the primary and improving performance.

Execution Sample

AWS

1. Create primary DB instance
2. Create read replica from primary
3. Replica syncs data continuously
4. Application sends reads to replica
5. Application sends writes to primary

This sequence shows how a read replica is created and used to improve read performance by offloading read traffic from the primary database.

Process Table

Step	Action	State Change	Result
1	Create primary DB instance	Primary DB is active	Primary ready for reads and writes
2	Create read replica	Replica instance created	Replica starts syncing data from primary
3	Replica syncs data	Replica data updated	Replica has near real-time copy of primary data
4	Application sends read requests	Reads directed to replica	Read load on primary decreases
5	Application sends write requests	Writes go to primary only	Primary handles all writes
6	Replica continues syncing	Replica stays updated	Read performance improved
7	Stop	N/A	Process ends as replica is serving reads

💡 Replica is serving read traffic, primary handles writes, improving overall performance

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
Primary DB	Not created	Active	Active	Active	Active	Active
Read Replica	Not created	Created	Syncing data	Serving reads	Serving reads	Serving reads
Read Load on Primary	High	High	High	Reduced	Reduced	Reduced
Write Load on Primary	High	High	High	High	High	High

Key Moments - 3 Insights

Why does the read load on the primary database decrease after creating a read replica?

Because read requests are redirected to the replica (see execution_table step 4), reducing the number of reads the primary must handle.

Does the read replica handle write requests?

No, all writes go to the primary database only (see execution_table step 5). The replica is read-only.

How does the replica stay up to date with the primary database?

The replica continuously syncs data from the primary (see execution_table step 3 and 6), keeping a near real-time copy.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the read load on the primary database decrease?

A Step 2

B Step 5

C Step 4

D Step 3

💡 Hint

Check the 'Read Load on Primary' state change column in the execution_table at step 4.

According to the variable tracker, what is the state of the read replica after step 3?

A Not created

B Syncing data

C Created but not syncing

D Serving reads

💡 Hint

Look at the 'Read Replica' row and the 'After Step 3' column in variable_tracker.

If the application sends write requests to the replica instead of the primary, what would change in the execution table?

A Replica would handle writes, which is not supported

B Write load on primary would increase

C Read load on primary would increase

D Replica would stop syncing data

💡 Hint

Refer to key_moments about write handling and execution_table step 5.

Concept Snapshot

Read replicas are copies of a primary database used to handle read requests.
They sync data continuously from the primary.
Writes always go to the primary.
This setup improves read performance by reducing load on the primary.
Applications direct reads to replicas and writes to the primary.

Full Transcript

Read replicas improve database performance by creating a copy of the primary database that handles read requests. The primary database handles all write operations. The replica continuously syncs data from the primary to stay updated. This reduces the read load on the primary, improving overall performance. The process starts by creating the primary database, then creating a read replica. The replica syncs data and serves read traffic while the primary handles writes. This separation of read and write traffic optimizes database responsiveness and scalability.

Practice

1. What is the main purpose of using read replicas in AWS databases?

easy

A. To store backups of the database

B. To handle more read requests and improve performance

C. To increase write speed on the main database

D. To encrypt data at rest automatically

Solution

1. Step 1: Understand the role of read replicas

   Read replicas are copies of the main database used to handle read traffic separately.

2. Step 2: Identify the performance benefit

   By offloading read requests to replicas, the main database is less busy, improving overall speed.

3. Final Answer:

   To handle more read requests and improve performance -> Option B

4. Quick Check:

   Read replicas improve read performance [OK]

Hint: Read replicas help with reads, not writes [OK]

Common Mistakes:

• Thinking read replicas speed up writes
• Confusing read replicas with backups
• Assuming read replicas encrypt data automatically

2. Which AWS CLI command correctly creates a read replica for an existing RDS instance named mydb?

easy

A. aws rds create-db-instance-read-replica --db-instance-identifier mydb-replica --source-db-instance-identifier mydb

B. aws rds create-db-instance --db-instance-identifier mydb-replica --source-db-instance-identifier mydb

C. aws rds create-read-replica --db-instance-identifier mydb-replica --source-db-instance mydb

D. aws rds replicate-db-instance --source mydb --target mydb-replica

Solution

1. Step 1: Identify the correct AWS CLI command for read replicas

   The correct command is create-db-instance-read-replica to create a read replica.

2. Step 2: Check the parameters

   The parameters --db-instance-identifier and --source-db-instance-identifier are required to specify the replica and source.

3. Final Answer:

   aws rds create-db-instance-read-replica --db-instance-identifier mydb-replica --source-db-instance-identifier mydb -> Option A

4. Quick Check:

   Correct AWS CLI syntax for read replica creation [OK]

Hint: Look for 'create-db-instance-read-replica' command [OK]

Common Mistakes:

• Using 'create-db-instance' which creates a new DB, not a replica
• Wrong command names like 'create-read-replica'
• Mixing source and target parameters

3. Given this AWS CLI command output snippet after creating a read replica:

{
  "DBInstanceIdentifier": "mydb-replica",
  "DBInstanceStatus": "creating",
  "ReadReplicaSourceDBInstanceIdentifier": "mydb"
}

What does the DBInstanceStatus value indicate?

medium

A. The read replica is ready and available for use

B. The read replica is being deleted

C. The read replica is currently being created and not ready yet

D. The read replica creation failed

Solution

1. Step 1: Understand the meaning of 'DBInstanceStatus'

   This field shows the current state of the database instance.

2. Step 2: Interpret the status 'creating'

   'creating' means the instance is in progress of being set up and is not yet ready.

3. Final Answer:

   The read replica is currently being created and not ready yet -> Option C

4. Quick Check:

   Status 'creating' means setup in progress [OK]

Hint: Status 'creating' means not ready yet [OK]

Common Mistakes:

• Assuming 'creating' means ready
• Confusing 'creating' with 'failed'
• Thinking 'creating' means deletion

4. You created a read replica but notice it is not receiving updates from the source database. What is a likely cause?

medium

A. The source database has no write traffic

B. The read replica was created in a different AWS region

C. The read replica is set to multi-AZ deployment

D. The source database is not configured for automated backups

Solution

1. Step 1: Understand replication requirements

   Read replicas require the source database to have automated backups enabled to support replication.

2. Step 2: Analyze the cause of no updates

   If automated backups are off, replication cannot start, so the replica won't receive updates.

3. Final Answer:

   The source database is not configured for automated backups -> Option D

4. Quick Check:

   Automated backups must be enabled for replication [OK]

Hint: Check if automated backups are enabled on source [OK]

Common Mistakes:

• Assuming region mismatch always blocks replication
• Confusing multi-AZ with read replica settings
• Thinking no write traffic stops replication

5. You have a high-traffic web app using an AWS RDS MySQL database. You want to improve read performance without affecting writes. Which setup is best?

hard

A. Create multiple read replicas and direct read queries to them

B. Increase the instance size of the main database only

C. Enable multi-AZ deployment without read replicas

D. Use a single read replica and send all traffic to it

Solution

1. Step 1: Identify the goal

   The goal is to improve read performance without slowing down writes.

2. Step 2: Evaluate options

   Creating multiple read replicas allows distributing read traffic, reducing load on the main DB and improving read speed.

3. Step 3: Compare other options

   Increasing instance size helps but may be costly and less scalable; multi-AZ improves availability, not read performance; a single replica may become a bottleneck.

4. Final Answer:

   Create multiple read replicas and direct read queries to them -> Option A

5. Quick Check:

   Multiple read replicas scale read performance best [OK]

Hint: Use many read replicas to spread read load [OK]

Common Mistakes:

• Relying only on bigger main DB instance
• Confusing multi-AZ with read scaling
• Using only one read replica for heavy reads