This article explains the Nginx master‑slave high‑availability architecture, describing the roles of master and slave nodes, the use of Keepalived for VIP failover via heartbeat detection, and provides configuration diagrams and code snippets to illustrate seamless traffic switching.
The article explores the evolution of database high‑availability architectures, compares mainstream solutions like Oracle's HA, RAC and ADG, examines domestic offerings such as GBase 8s with HAC, RHAC and SSC clusters, and provides practical guidance for selecting cost‑effective HA designs to ensure continuous business operations.
iQIYI’s custom MySQL HA solution replaces the single‑point‑failure MHA manager with a Raft‑based trio of HA Masters and HA Agents that continuously monitor instances, automatically perform same‑DC, cross‑DC, or cross‑region failovers, reconcile diff binlogs, ensure data consistency, and integrate with CMDB, tracing and chaos‑engineering platforms.
The article reviews common MySQL high‑availability solutions—including shared‑storage SAN, DRBD disk replication, keepalived/heartbeat, MHA, ZooKeeper‑based HA, Galera/PXC clusters, and proxy middleware—detailing their architectures, advantages, limitations, and suitability for different business and operational requirements.
