How to Create an AWS MySQL RDS Read Replica

Why?

Read Replica provides you extra read-only power, so you can direct your heavy load SELECT (OLAP) queries to the read replica, while the main RDS cluster can serve your critical OLTP transactions.

How?

To create a MySQL read replica in Amazon Web Services (AWS) using Amazon Relational Database Service (RDS), you can follow these steps:

1. Sign in to the AWS Management Console and navigate to the RDS dashboard.
2. In the navigation pane, click on the "Instances" menu item.
3. Select the instance that you want to use as the source for the read replica.
4. From the "Actions" dropdown menu, select "Create read replica".
5. In the "Create Read Replica" dialogue box that appears, you can specify the following options:

• The instance identifier for the read replica. This should be unique within your AWS account.
• The instance class for the read replica. You can choose from a range of instance sizes based on your performance and capacity needs.
• The storage type and size for the read replica. You can choose between magnetic and SSD storage, and specify the size in gigabytes.
• The availability zone for the read replica. This determines the geographical region where the read replica will be located.
• The security group and VPC for the read replica. You can use the same security group and VPC as the source instance, or choose different ones.

6. Click "Create read replica" to create the read replica. It will be created as a new RDS instance, and will be automatically replicating data from the source instance.

You can monitor the progress of the read replica creation process by checking the "Status" column on the RDS dashboard. When the status of the read replica changes to "available", it is ready to use.

Keep in mind that read replicas are designed to be used for read-only workloads, and you cannot write to them directly. Any writes to the source instance will be replicated to the read replica, but you cannot write directly to the read replica.

Keep Performing, Moshe Kaplan

Monitoring Dashboard Principles for AWS Serverless System

A monitoring dashboard for a serverless system would typically include information about the health and performance of the system, such as the number of requests being handled, the average response time, and any errors or issues that are occurring. The specific metrics and information included on a monitoring dashboard can vary depending on the specific system and the needs of the users. Some common metrics that might be included on a monitoring dashboard for a serverless system include:

1. Request count: The number of requests being handled by the system.
2. Error rate: The percentage of requests that are resulting in errors.
3. Latency: The average time it takes for a request to be processed.
4. CPU and memory usage: The amount of CPU and memory resources being used by the system.
5. Throughput: The amount of data being processed by the system.
6. Scalability: Information about how the system is scaling up or down in response to changes in workload.

These are just some examples of the types of information that might be included on a monitoring dashboard for a serverless system. The exact metrics and information displayed on the dashboard will depend on the specific needs of the system and the users. 

Keep Performing,

Moshe Kaplan