ความพร้อมใช้งานสูงและการกู้คืนจากภัยพิบัติ

Welcome to High Availability (HA) and Disaster Recovery (DR)! These are critical concepts for any successful SaaS product.

In this lesson, we'll explore how to design systems that stay online and recover quickly from unexpected problems.

Imagine your SaaS product goes down. What happens?

• Lost Revenue: Customers can't use your service.
• Damaged Trust: Users lose faith in your reliability.
• SLA Breaches: You might violate Service Level Agreements.

HA aims to minimize these negative impacts by keeping your service running.

The core principle of High Availability is redundancy. This means having duplicate components for critical parts of your system.

If one component fails, another identical one can take over immediately, preventing a complete outage. Think of it like having a spare tire!

Load balancers are key to distributing incoming network traffic across multiple servers. They ensure no single server is overwhelmed and can redirect traffic away from unhealthy servers.

• Distributes user requests.
• Identifies and isolates failing servers.
• Improves response times and throughput.

When a server or service fails, an automatic failover mechanism detects the issue and seamlessly switches to a healthy, redundant component.

This process is designed to be quick and transparent to the end-user, minimizing service disruption without manual intervention.

In an active-passive HA setup, one server (the active one) handles all requests, while another (the passive or standby one) waits idly.

If the active server fails, the passive server takes over. It's simpler to manage but resources for the passive server are underutilized.

With an active-active HA setup, all redundant servers are simultaneously handling requests.

This setup offers better resource utilization and can handle higher loads. If one server fails, the remaining active servers simply pick up the extra load.

While HA focuses on keeping individual services running, Disaster Recovery (DR) deals with larger-scale outages, like an entire data center or cloud region going offline.

DR plans ensure your entire SaaS product can be restored and brought back online in a different location after a major catastrophe.

Two key metrics for DR are:

• Recovery Point Objective (RPO): The maximum acceptable amount of data loss, measured in time (e.g., 1 hour of data).
• Recovery Time Objective (RTO): The maximum acceptable downtime before your service is restored, also measured in time (e.g., 4 hours).

These define your acceptable risk for data loss and service interruption.

A fundamental part of DR is a robust backup and restore strategy. This involves:

• Regularly backing up your data and configurations.
• Storing backups securely, often in different geographic locations.
• Testing your restore procedures frequently to ensure they work when needed.

Backups are your ultimate safety net against data loss.

Which of the following best describes the primary goal of a Disaster Recovery (DR) plan, as opposed to High Availability (HA)?

You've learned about the critical importance of High Availability and Disaster Recovery for SaaS.

• HA keeps services running despite component failures using redundancy, load balancing, and failover.
• DR ensures recovery from catastrophic events using RPO/RTO metrics and backup strategies.

Implementing these strategies ensures your SaaS product remains reliable and trustworthy for your users!