This article explains how to build a highly available Nginx deployment using a master‑slave architecture combined with Keepalived, detailing the role of virtual IPs, the failover mechanism, and the step‑by‑step process that ensures 99.99% uptime.
The article analyzes a JD interview question on scaling a MySQL order table from 100 million to billions of rows, detailing four practical expansion strategies—stop‑service migration, double‑write migration, ShardingSphere middleware, and dual‑VIP routing—each with step‑by‑step procedures, code samples, risk assessments, and validation methods to enable near‑instant capacity growth without service interruption.
This article explains how Nginx's master‑slave (primary‑backup) setup, combined with Keepalived and a virtual IP, provides high‑availability for web and API services by automatically detecting failures, shifting the VIP, and allowing the backup server to take over without service interruption.
This article details how the Kube-OVN community extended the CNI for edge cloud scenarios by adding security‑group based access control, high‑availability virtual IP support, live‑migration‑friendly networking, and smart‑NIC hardware offload, including implementation steps, CRD designs, and relevant pull‑request references.
This article explains why Redis is widely used, defines high availability for Redis services, enumerates common failure scenarios, evaluates four architectural solutions—including single‑instance, master‑slave with one, two, and three Sentinel instances—and finally presents a production‑grade HA design using three Sentinels and a virtual IP.
The article reports on the seventh China International 'Internet+' College Student Innovation and Entrepreneurship Competition, highlighting its new industry challenge track focused on virtual IP, the award-winning solution from Beijing Institute of Technology using AI-driven digital human production, and Tencent Advertising's virtual human creative service for marketing.
This article explains how to build a highly available Redis service using Redis Sentinel, covering failure scenarios, design principles, four architectural options, the final three‑Sentinel solution with virtual IP, and practical operational tips for ensuring continuous service.
This article explains how to build a highly available Redis service by analyzing common failure scenarios, evaluating single‑instance, master‑slave with one or multiple Sentinel processes, and ultimately recommending a three‑Sentinel architecture combined with a virtual IP for seamless client usage.
This article explains why Redis needs high availability, defines common failure scenarios, compares several HA solutions, and walks through four deployment patterns—culminating in a three‑Sentinel architecture with a virtual IP to provide seamless, fault‑tolerant Redis access.
This tutorial walks you through configuring Keepalived for single‑instance master‑backup failover and dual‑instance dual‑master high‑availability setups, covering preparation, installation, configuration file edits, service startup, verification of virtual IP migration, and practical verification commands.
This lesson explains the value and implementation of high‑availability systems, explores load‑balancing concepts, features, and scenarios—including health checks, session persistence, and scheduling algorithms—and introduces virtual IP solutions for robust cloud infrastructure.
This article walks through the design of a highly available Redis deployment, explains common failure scenarios, compares single‑node, master‑slave, and multi‑Sentinel architectures, and shows how adding a virtual IP and three Sentinel instances can provide robust HA while keeping client usage simple.
This article explains why Redis is a popular in‑memory key‑value store, defines high availability, enumerates failure scenarios, and walks through four incremental architectures—single instance, master‑slave with one Sentinel, dual Sentinel, and three‑Sentinel with VIP—to achieve a robust, production‑grade Redis deployment.
This article explains how to design and deploy a fault‑tolerant Redis architecture using master‑slave replication, multiple Sentinel instances, and a virtual IP so that the service remains available despite process crashes, server outages, or network partitions.
This article explains how to design and implement a highly available Redis deployment using master‑slave replication, multiple Redis Sentinel instances, and a virtual IP to provide seamless failover while maintaining simple client connectivity, covering failure scenarios, architecture choices, and practical configuration tips.
This article explains how to design a highly available Redis service using Sentinel, compares four deployment architectures, discusses failure scenarios and quorum requirements, and shows how a virtual IP can provide a single‑point access while ensuring continuous service.
This article explains how to build a highly available Redis deployment by defining HA requirements, analyzing failure scenarios, and progressively implementing solutions from a single instance to a three‑sentinel architecture with virtual IP failover for seamless client access.
