The article explains eBay's use of MongoDB to create highly available, fault‑tolerant multi‑data‑center architectures, detailing design patterns, replica set configurations, read/write strategies, and recent MongoDB features that enable scalable, mission‑critical applications.
This article explains why high availability is critical for internet services, outlines key techniques such as stateless design, service discovery, heartbeat checks, idempotent operations, load balancing, throttling, caching, and micro‑service architecture, and discusses the operational challenges and monitoring tools needed to maintain resilient, scalable systems.
The article discusses how to achieve high availability for large‑scale internet services by adopting stateless architecture, service discovery and registration, heartbeat monitoring, idempotent design, retry mechanisms, rate limiting, caching, and micro‑service decomposition to handle machine failures, network glitches, and high concurrency.
This article reviews Alibaba Cloud's high‑performance load‑balancing solution, explaining the evolution from basic load‑balancing concepts to the architecture of LVS and Tengine, detailing their modes, optimizations, high‑availability designs across groups, AZs and regions, and outlining current use cases and future directions.
This article outlines essential principles for designing high‑concurrency and high‑availability systems, covering stateless architecture, service decomposition, caching strategies, message queues, data heterogeneity, degradation, rate limiting, traffic switching, rollback, and comprehensive business design rules such as idempotency, anti‑duplication, and documentation.
This article outlines essential high‑concurrency and high‑availability principles—including stateless design, service decomposition, caching strategies, message queues, data heterogeneity, degradation, rate limiting, traffic switching, and rollback mechanisms—to help architects build scalable, reliable, and resilient systems.
This article explains how integrating IP SAN and FC SAN with FCoE simplifies data‑center networks, reduces hardware and power consumption, improves flexibility and reliability, and details the deployment modes, access‑layer design, high‑availability considerations, and traffic models for a unified LAN/SAN architecture.
A sudden surge of traffic triggered by a celebrity relationship announcement caused a Weibo outage, prompting frantic reactions from developers, operations, and management, and leading to an in‑depth analysis of high‑availability architecture, elastic scaling, hybrid‑cloud DCP platforms, and Docker‑based service deployment.
The article reviews Oracle's high‑availability and sharding advances in 18c, including RAC Sharding 2.0 and Active Data Guard features, and examines MySQL 8.0's major improvements such as the removal of MyISAM, data‑dictionary optimizations, self‑tuning, enhanced security, and new performance capabilities, while also comparing MySQL with PostgreSQL.
This article explains the evolution of storage, the shift toward cloud‑native storage solutions, and details the network architecture, latency considerations, and operational challenges involved in building dual‑active data center storage systems for high‑availability enterprise environments.
The article describes the motivation, architecture, FullNat forwarding process, high‑availability mechanisms, and performance‑optimizing techniques of TVS, a custom four‑layer load‑balancing platform built to overcome LVS limitations and meet the company’s demanding traffic and reliability requirements.
The article explains EMC vPlex's evolution, dual‑active Metro and Geo configurations, distributed cache coherence, storage virtualization, and integration with RecoverPoint, highlighting how these technologies enable high‑availability, low‑latency data access across multiple data‑center sites.
This article explains HDS’s High Availability Manager (HAM) and Global Active Device (GAD) technologies, detailing how they virtualize mirrored LUNs, use TrueCopy replication, arbitration mechanisms, and various network topologies to provide seamless active‑active storage, support for NAS, and flexible clustering across data centers.
PhxQueue, an open‑source, Paxos‑based distributed queue from WeChat, delivers at‑least‑once delivery, synchronous disk flushing, strict ordering, multi‑subscription, and high availability, outperforming Kafka in reliability and latency while maintaining comparable throughput, as demonstrated through detailed design, performance, and failover analyses.
This article explains Alibaba Cloud's Server Load Balancer (SLB) architecture and its four-tier high‑availability design—application processing, cluster forwarding, cross‑zone disaster recovery, and cross‑region disaster recovery—detailing both product features and user‑side best practices.
This article explains why Kafka introduced High Availability in version 0.8, covering the necessity of data replication and leader election, the internal replication and ACK mechanisms, Zookeeper metadata structures, broker failover procedures, and the command‑line tools that help manage and rebalance a Kafka cluster.
This article examines the principles, features, and implementation details of distributed scheduling for big‑data ETL pipelines, covering decentralised schedulers, host selection strategies, fault‑tolerance, operator abstraction, elasticity, trigger mechanisms, visual monitoring, alarm handling, data fan‑in/fan‑out, parameter consistency, real‑time quality checks, lineage tracking, and field‑level traceability.
This article presents a step‑by‑step operations‑focused roadmap for evolving a website from a single‑server prototype to a highly available, horizontally scalable architecture using load balancing, caching, database replication, service‑oriented design, DNS round‑robin, CDN, and disaster‑recovery techniques.
This article explains how to protect Redis deployments from single‑point failures by using master‑slave replication, manual failover procedures, and the automated high‑availability Sentinel solution, providing practical guidance for reliable disaster recovery in non‑clustered environments.
This article explains UDB's high‑availability architecture, detailing its dual‑node design with virtual IP and HAProxy, and describes the kernel‑level optimizations applied to MySQL's native semi‑synchronous replication, relay log handling, master.info management, and lock contention to boost stability and performance.
This article details UDB's high‑availability architecture and four kernel‑level optimizations—binlog replication, relay‑log recording, master.info handling, and relay‑log locking—that together improve MySQL semi‑synchronous replication performance and reliability.
This article explains how a high‑traffic e‑commerce platform uses RabbitMQ for reliable, high‑throughput order processing, covering its core concepts, routing patterns, clustering, high‑availability queues, client support, management tools, and step‑by‑step cluster deployment.
This article traces Meituan‑Dianping's MySQL high‑availability journey, detailing the legacy MMM system, the transition to MHA, integrations with Zebra and Proxy middleware, current challenges, and future designs such as distributed agents, semi‑sync replication, and MySQL Group Replication.
AliSQL X‑Cluster is Alibaba's MySQL‑compatible distributed database that integrates the X‑Paxos consensus protocol to provide strong consistency, multi‑region deployment, low‑cost replica types, asynchronous transaction commit, hotspot‑update optimizations and superior performance compared with native MySQL and Group Replication, while offering flexible online configuration and robust failover mechanisms.
This article outlines comprehensive MySQL best practices, covering development and operational standards, high‑availability architecture choices such as Keepalived, MHA and Percona XtraDB Cluster, sharding strategies (vertical and horizontal), and how Redis can be leveraged to offload read pressure.
This article explains website availability metrics, fault‑weight scoring, layered high‑availability architecture, session management strategies, reusable service design, data redundancy, quality assurance processes, and monitoring practices essential for maintaining reliable large‑scale web systems.
The CCF TF Architecture SIG hosted a densely attended microservices practice seminar in Beijing, featuring leading experts from 25 top tech companies who shared deep insights on service discovery, high‑availability architectures, Spring Cloud adoption, and large‑scale microservice frameworks such as Vintage, OCTO, and rest.li.
This article explains the design and implementation of PhxSQL, a MySQL‑compatible high‑availability solution that uses a reliable log storage based on Paxos, Proxy request forwarding, automatic master election, and other mechanisms to overcome native MySQL replication flaws and provide strong data consistency and fault‑tolerant performance.
This article explains Memcached's slab allocator memory management, key concepts like items, chunks, slab classes and pages, the calcium problem, and how master‑slave double‑layer and L1 cache architectures enable high concurrency, high availability, and linear scaling.
This article details Ele.me's design and implementation of a MySQL bidirectional replication component (DRC) that enables sub‑second, high‑throughput data synchronization across Beijing and Shanghai data centers, addressing latency, consistency, and failover challenges in a multi‑active environment.
This article explains how to design and implement dual‑active storage solutions combined with virtualization and application clustering, covering industry requirements, storage vendor options, physical and virtual deployment models, and the role of cloud storage and OpenStack Ironic.
This article traces Meituan‑Dianping's MySQL high‑availability journey from the early MMM replication manager to the modern MHA‑Zebra and MHA‑Proxy solutions, compares each architecture, highlights their shortcomings, and outlines future directions such as distributed agents, semi‑sync replication, and Paxos‑based MySQL Group Replication.
After initially focusing on a distributed MySQL system, the author describes why open‑source HA solutions like MHA were unsuitable, then details the design and implementation of a 4‑layer NAT‑based proxy (RDS) and a more advanced 7‑layer application‑level proxy, highlighting features such as authentication, load balancing, read/write splitting, and multi‑datacenter awareness.
This article explains why Paxos is needed for consistency in distributed systems, details its roles and three-phase protocol, illustrates the algorithm with a real‑world analogy, and shows how Paxos underpins high‑availability database replication such as MySQL binlog synchronization.
This article explains why Redis high‑availability is essential, details the inner workings of Redis Sentinel, compares several HA architectures—including Sentinel with DNS or VIP, client‑side Sentinel, Keepalived/Haproxy, Redis Cluster, Twemproxy, and Codis—lists their pros and cons, and shares practical best‑practice recommendations for building reliable Redis deployments.
This article walks through the fundamentals of InfluxDB as a time‑series database, demonstrates how to write data via its HTTP API, and shows how to configure Grafana for real‑time visualization, high‑availability deployment, and alerting in a big‑data monitoring scenario.
This article provides a comprehensive overview of large‑scale website architecture, covering key metrics, evolutionary stages, core design patterns, performance testing, high‑availability strategies, scalability techniques, and security measures essential for building and operating robust web systems.
This article explores core distributed system design principles, detailing the CAP theorem and its implications, the BASE extension, shared‑nothing architecture, various load‑balancing algorithms and deployment modes, as well as high‑availability strategies such as active‑standby, active‑active, and clustering to eliminate single points of failure.
This guide details the step‑by‑step process for replacing a faulty ZooKeeper node (myid 5) in a five‑node cluster, covering configuration updates in zoo.cfg, Hadoop’s hdfs‑site.xml, yarn‑site.xml, HBase‑site.xml, and the required service restarts to ensure continuous high‑availability.
This guide walks through setting up a Redis high‑availability solution using master‑slave replication, Redis Sentinel for automatic failover, and a floating VIP to provide a stable endpoint, covering environment preparation, configuration files, firewall rules, testing, and client integration.
The article explains high‑availability concepts, compares typical MySQL HA architectures—including replication, clustering, and Paxos‑based solutions—and presents UDB’s dual‑master semi‑synchronous design with a Proxy layer that ensures automatic failover, data consistency, and operational resilience.
This article presents a comprehensive overview of MySQL high‑availability solutions, covering classic HA architectures, synchronization tools such as MHA, MMM, HA‑JDBC, Galera and Group Replication, and shares NetEase's practical implementations using distributed databases and keepalive‑based failover.
This article chronicles the evolution of Meituan's food‑delivery order system from a simple modular prototype to a distributed, high‑performance, highly available architecture, detailing the business characteristics, architectural milestones, performance optimizations, consistency safeguards, scalability techniques, and intelligent operations that enable handling millions of orders per day.
In this talk, Alibaba expert Mu Jian shares how the massive Taobao e‑commerce platform achieved high availability through layered networking, cache design, OS‑level tuning, rate limiting, disaster‑recovery planning, and cloud‑native architectures, offering practical guidance for building resilient systems at scale.
This article reviews core database high‑availability technologies—including IBM DB2 HADR, HACMP clustering, SQL and Q replication, storage‑level disaster recovery, and DPF considerations—explaining their mechanisms, suitable scenarios, and practical deployment tips for enterprise environments.
This article explains the design and implementation of XDB, a MySQL high‑availability framework used by Baidu Waimai, detailing its component architecture, Horus state‑machine based failover, monitoring mechanisms, log management, and real‑world deployment experiences.
Meituan’s Leaf system merges segment‑based caching with Snowflake‑style bit fields to deliver globally unique, trend‑increasing 64‑bit IDs at ultra‑low latency, using double‑buffered DB segments, master‑slave MySQL replication, Zookeeper‑assigned worker IDs, and clock‑rollback safeguards, achieving ~50 k QPS and 1 ms 99.9th‑percentile response across billions of daily IDs.
This article introduces XPipe, a framework designed by Ctrip to enable Redis multi‑data‑center replication, ensure high availability through keeper and MetaServer components, and provide reliable disaster‑recovery (DR) switching while maintaining low latency and data consistency.
This article explains how to deploy a Redis master‑slave cluster with Sentinel for high availability, details application configuration, highlights a subtle issue where Redis passwords are automatically rewritten after failover, and provides three remediation approaches including a source‑code patch with GitHub links.
This article examines the architecture of Weibo's high‑availability advertising platform, covering match service design with OpenResty, index sharding, business logic optimization, dynamic auto‑scaling, and a real‑time monitoring pipeline to ensure stable, high‑performance ad delivery at massive scale.
The article explains how achieving high availability through data redundancy introduces consistency challenges that in turn affect performance, and it reviews partitioning, mirroring, consistency models, replication architectures, and two/three‑phase commit protocols in distributed systems.
This article details Alibaba Group's journey of transforming its GitLab deployment from a single‑node setup to a distributed, sharded architecture that handles tens of millions of daily requests, achieves near‑perfect reliability, and incorporates performance, monitoring, and disaster‑recovery innovations.
This article explains how a decentralized microservice and SOA architecture, combined with cloud deployment, service registration, gateways, and unified APIs, enables high‑performance, high‑availability, and low‑coupling smart campus systems that support both mobile and PC applications while simplifying development, testing, and operations.
This article explains the principles of load balancing, distinguishes stateless service and stateful data balancing, describes DNS, hardware and software solutions such as F5, HAProxy, LVS, and GSLB, and illustrates real‑world implementations at Alibaba and Tencent while offering practical guidance on sharding, caching, and fault tolerance.
This article provides a comprehensive overview of Linux Virtual Server (LVS) load‑balancing clusters, detailing core concepts, packet‑flow mechanisms, key terminology, NAT/DR/TUN modes, scheduling algorithms, step‑by‑step configuration scripts, and high‑availability setup with keepalived, all illustrated with diagrams and command examples.
This article examines various business load scenarios for a logistics management system and presents four progressive load‑balancing architectures—ranging from simple Nginx/Haproxy to DNS round‑robin with LVS and Keepalived—while defining key performance terms and outlining future discussion topics.
This article provides a comprehensive guide to Inceptor Server HA, covering its high‑availability architecture, configuration steps, required parameters, connection strings, failover behavior, and the HA Tools utility for monitoring and managing master‑standby switches.
This guide walks through building a SQL Server Failover Cluster on QCloud, covering architecture choices, network layout, required roles like DTC, step‑by‑step installation on two nodes, configuration of virtual IPs, and recommendations to prefer AlwaysOn or PaaS solutions for production reliability.
This step‑by‑step guide walks readers through securely building a four‑node SQL Server Failover Cluster on Tencent Cloud—covering jump‑server setup, domain controller and storage gateway configuration, AD account creation, internal CLB and DNS setup, network and iSCSI storage configuration, CSV and quorum settings, and final failover verification.
This article explains the theory and practical techniques behind synchronizing state across data centers using a two‑site three‑center model, covering distributed protocols like Paxos and Raft, CAP trade‑offs, latency challenges, and high‑availability designs for robust database replication.
This article details Hengfeng Bank's practical experience with OpenStack, covering why the bank chose the open‑source cloud platform, its multi‑site deployment architecture, high‑availability design, management practices, and lessons learned from operating a large‑scale financial cloud environment.
This guide explains what Twemproxy is, its features and limitations, and provides step‑by‑step instructions for installing, configuring, and testing the proxy with two Redis instances, plus high‑availability strategies using HAProxy and Sentinel.
This article explains what an LVS cluster is, outlines its types (LB, HA, HP), details common LVS deployment modes (nat, dr, tun) and their features, describes scheduling algorithms, and provides practical ipvsadm commands and configuration examples for building and managing high‑availability Linux load‑balancing clusters.
This article explores core system architecture concepts—including the CAP theorem and its BASE extension, the shared‑nothing design, various load‑balancing algorithms and deployment modes, and high‑availability patterns such as active‑standby, active‑active and clustering—providing practical guidance for building scalable, reliable distributed applications.
This article summarizes the evolution, patterns, and five core factors—performance, availability, scalability, extensibility, and security—of large‑scale website architecture, covering server tiers, caching, clustering, load balancing, data redundancy, and security measures.
The article introduces the need for a distributed configuration platform, outlines its typical scenarios and essential characteristics, and details the lightweight open‑source implementation Diablo—including its architecture, data model, Redis storage, client behavior, real‑time update mechanisms, and deployment recommendations.
The article chronicles the Qinglong logistics platform from its 2012 MVP launch through successive versions to a smart‑logistics system, detailing architectural evolution, high‑availability, performance, data‑consistency strategies, and user‑experience practices that underpin large‑scale backend development.
The 2016 China Oracle Database Usage Report, based on health‑check data from 1,841 instances across 18 industries, provides a multi‑dimensional analysis of version distribution, operating system choices, host and storage configurations, data scale, high‑availability setups, and top failure types, offering a comprehensive view of Oracle adoption and challenges in the Chinese market.
Zhou Tang, head of WeChat Pay operations at Tencent, shares how his team built a massive MySQL‑based payment platform handling up to 150 k transactions per second, covering background, DB‑CMDB design, change management, monitoring, security, high availability, and why Golang became their core development language.
This article explains how AliCloudDB supports the massive traffic of Alibaba’s Double‑11 shopping festival through elastic scaling (both in‑place and cross‑machine upgrades), secure and standard access paths, robust architecture design, read‑write separation, engine and index optimization, high‑availability configurations, performance tuning, and disaster‑recovery strategies.
This article explains Redis fundamentals, its key‑value storage model, advanced data structures, persistence mechanisms (RDB and AOF), replication architecture, and how Sentinel provides automated failover and high‑availability management, complemented by practical configuration examples and performance considerations.
This article explains MySQL's asynchronous, semi‑synchronous, and Group Replication mechanisms, compares their trade‑offs, details Group Replication’s certification‑based full‑sync workflow, lists its features and limitations, and provides a complete configuration and maintenance guide for a three‑node cluster.
DBProxy, an open‑source MySQL middleware derived from Atlas, offers horizontal scaling, read/write separation, load balancing, advanced blacklist filtering, dynamic configuration, and numerous bug fixes, positioning it as a mature, high‑availability solution for enterprise database environments.
This article explains why MySQL master‑slave replication is essential for high availability, describes the replication mechanism, provides detailed configuration commands for both master and slave servers, and shows how to test and recover synchronization when inconsistencies occur.
The talk details how Alibaba tackled the massive technical challenges of Double 11 over eight years by evolving a highly available, scalable architecture through capacity planning, distributed middleware, hybrid‑cloud deployment, online stress testing, and fine‑grained traffic control to balance cost, performance, and user experience.
An in‑depth look at WeChat’s Mars library reveals how a cross‑platform, high‑availability network component was designed, evolved through three phases, tackled real‑world mobile challenges, and was refactored and open‑sourced to support Android, iOS and other platforms.
This article explains how to standardize and automate MySQL management at scale, covering dedicated instance deployment, configuration consistency, multi‑instance creation, metadata collection, backup, monitoring, high‑availability with Zookeeper, and task orchestration using DBTask to achieve rapid, reliable database services.
This article introduces MHA (Master High Availability) for MySQL, explains its architecture, outlines required hardware and software configurations, provides detailed commands to set up master and slave nodes, create configuration files, and demonstrates how to start and verify the high‑availability cluster.
This article details Alibaba's eight‑year journey of scaling its Double 11 shopping festival by evolving high‑availability middleware, capacity planning, unit‑based architecture, hybrid cloud and automated traffic control to achieve reliable, cost‑effective performance at massive peak loads.
This article presents a comprehensive guide on building a VOIP service for overseas users, covering VOIP fundamentals, open‑source PBX selection, SIP client libraries, demo deployment, load‑balancing with Kamailio, high‑availability via Keepalived, NAT handling, TLS/SRTP support, and troubleshooting techniques.
This article explains how to standardize and automate MySQL operations—including multi‑instance deployment, metadata collection, monitoring, backup, and high‑availability using Zookeeper—so that large‑scale database services can be provisioned, managed, and scaled with minimal human intervention.
The article details Ctrip's call‑center architecture evolution, describing the multi‑layer active‑active design, public access, application and client layers, unified login mechanisms, operational challenges, disaster‑recovery drills, and future plans for software‑only and mobile agents, illustrating practical SRE principles in a large‑scale telephony system.
This guide walks through the principles of Keepalived, its VRRP‑based architecture, and step‑by‑step configuration of a dual‑master LVS high‑availability cluster, covering prerequisites, installation, keepalived setup, real server configuration, testing failover, and handling complete node failures.
This article details Qunar's comprehensive MySQL backup and recovery platform, covering high‑availability concepts, backup types, tool selection, multi‑channel architecture, storage solutions, automation, and operational lessons for scaling DBA operations across large‑scale deployments.
This guide explains how to use the Perl‑based MMM tool to monitor and manage MySQL master‑master replication, covering its advantages, working principle, detailed server configurations, connection steps, master‑slave testing, and high‑availability failover demonstrations.
This guide walks through extending MySQL 5.6.32 by adding a new SQLCOM_STOP_SLAVES command that stops all replication slaves, detailing modifications to lex.h, sql_cmd.h, sql_yacc.yy, sql_parse.cc, and mysqld.cc, along with compilation tips and troubleshooting steps.
PhxSQL is an open‑source, MySQL‑compatible relational database cluster that provides high availability and strong data consistency through a single‑master multi‑slave architecture, automatically switching masters when over half the nodes are alive, without relying on external services like Zookeeper, and requiring no code changes for migration.
This guide details a complete high‑availability architecture that separates static and dynamic DiscuzX traffic using HAProxy, adds Varnish caching, configures Nginx with NFS shares, sets up keepalived for HA, and provides all necessary installation commands, configuration snippets, and testing results.
This guide walks you through configuring a simple Redis master‑slave setup, covering the benefits, step‑by‑step file modifications, essential replication directives, testing procedures, and common pitfalls to ensure high availability and read/write separation.
The conference featured a series of high‑availability architecture talks covering performance‑driven design, RPC framework resilience, big‑data platform evolution, MySQL cluster consistency, and cloud infrastructure best practices, presented by experts from 58.com, Alibaba, Tencent, Baidu, and others.
This article explains practical techniques for improving web service availability—such as static‑dynamic separation, CDN acceleration, distributed file systems, service decomposition, and database sharding—while minimizing code changes and addressing common scaling challenges.
In this interview, Lu Pengcheng, a platform architect at Mogu Street, discusses the company’s large‑scale e‑commerce architecture, the evolution of its monitoring platform, design choices for high‑availability distributed systems, and future open‑source plans, providing practical insights for engineers and technical managers.
This article explains the core differences between distributed systems and clusters, detailing their architectures, efficiency goals, typical use cases such as Hadoop MapReduce and load‑balancing clusters, and outlines key concepts like scalability, high availability, load balancing, and error recovery.
This article explains the fundamentals of database sharding, including horizontal partitioning concepts, routing rules, and various sharding strategies such as range, hash, and mapping tables, and how clustering, load balancing, and read/write separation improve scalability, availability, and performance for large‑scale internet applications.
This article outlines comprehensive e‑commerce platform architecture practices—including caching strategies, indexing, parallel and distributed computing, load balancing, sharding, high availability, monitoring, resource optimization, and messaging—to improve system performance, scalability, and reliability under high concurrency.
This article explains various service degradation strategies—including interface and page refusal, delayed persistence, and persistent‑layer restrictions—along with management approaches and implementation points such as middleware control, NGINX+LUA page blocking, and data‑operation rules, to keep core functions running under high server pressure.
This guide outlines a step‑by‑step strategy for designing a highly available, secure, and scalable website architecture, covering domain acquisition, CDN deployment, image caching, data center selection, monitoring, DDoS mitigation, redundancy, server configuration, database replication, testing environments, and operational best practices.
This guide walks through installing MySQL Shell and Router, deploying three local MySQL instances, creating an InnoDB cluster, adding the instances, configuring MySQL Router, and testing failover to demonstrate a simplified high‑availability setup.
Meituan’s Database Automation Platform evolved from a simple Django‑based 1.0 system into a modular 2.0 architecture using CMDB, RabbitMQ, and Celery, standardizing metadata, providing self‑service APIs, and automating tasks such as cluster provisioning, online schema changes, and high‑availability failover, now handling hundreds of daily operations for over a thousand developers while planning further component‑library refactoring.
This article walks through a real‑world upgrade from SQL Server 2008 R2 to 2014, detailing background analysis, data collection, solution design, detailed investigation, testing, performance baselines, side‑by‑side migration, cluster setup, application changes, and common pitfalls such as CDC issues, index‑rebuild logging, and query slowdowns.
