▸ Implemented Route53 Reader and Writer Endpoints

Reader and Writer Endpoints were introduced using Amazon Route53, ensuring that read traffic was balanced across replicas while write traffic was routed to the master node. This helped alleviate the load on the master, improving system responsiveness and performance.

‍

▸ Performance Optimization

Database parameters were fine-tuned to optimize resource utilization and performance. Query Optimization: Inefficient queries were rewritten, and index optimization was applied to improve query execution times. Large tables were archived to reduce their size, improving query performance and response times.

‍

▸ Deployment of Multi-AZ Configuration

The RDS instance was configured in Multi-AZ mode, ensuring high availability by automatically provisioning a standby replica in another Availability Zone (AZ). Automatic failover was implemented to ensure seamless continuity in case of hardware failure or network disruption.

‍

▸ Failover and Monitoring

Regular tests were conducted to validate the automatic failover functionality, ensuring minimal downtime during failover events. AWS CloudWatch alarms were set up to monitor database health and trigger alerts during failovers.

‍

Implementation

Deployment Pattern

The chosen deployment pattern is Multi-AZ Deployment with automatic failover. This pattern is used to increase availability and resilience in Amazon RDS.

‍

Primary Instance and Standby Replica

The primary database instance is located in one availability zone (AZ), and a standby replica is automatically created in another AZ. In the event of a failure or maintenance event, RDS automatically switches to the standby replica.

‍

Automatic Failover

This approach ensures that any instance-level failure (e.g., hardware failure or network disruption) triggers an automatic failover to the standby instance in a different availability zone, minimizing downtime and ensuring continuous availability.

‍

Multi-AZ Configuration

During the initial setup, the RDS instance was configured to run in Multi-AZ mode. This involves Amazon RDS automatically provisioning a synchronous standby replica in another availability zone within the same region.

‍

Failover Testing

Regular failover tests were performed to validate the failover mechanism. The RDS instance was manually rebooted to simulate an outage, ensuring that the standby replica took over seamlessly.

‍

Storage and Replication

Storage-level replication between the primary instance and standby replica is synchronous, ensuring that there is no data loss in case of a failover.

‍

Monitoring and Alerts

CloudWatch alarms were set up to monitor database health, and in the event of a failure, alerts are triggered to inform the team about the automatic failover.