This article provides a detailed overview of Huawei's dual-active storage solutions, describing the VIS gateway architecture, stretched VCS clusters, HyperMetro active-active implementation, network and hardware considerations, replication mechanisms, distributed locking, and performance optimizations for long-distance data-center deployments.
PhxQueue is a Tencent‑open‑source, Paxos‑based distributed queue that delivers at‑least‑once delivery, synchronous disk flushing, strict ordering, multi‑subscription, and high throughput, outperforming Kafka in reliability and failover scenarios while supporting massive workloads such as WeChat Pay.
This article details how Tencent's AMS system was analyzed, traffic‑estimated, and redesigned for high‑availability during the QQ Spring Festival Red Packet event, covering architecture mapping, scaling strategies, overload protection, flexible availability, disaster recovery, monitoring, and practical lessons learned.
This article describes how Alibaba Group transformed its GitLab platform from a single‑node deployment to a distributed, sharded architecture with proxy services, performance optimizations, multi‑datacenter backup, and automated operations to support millions of users and dramatically increase request throughput.
This article describes Alibaba's extensive use of HBase, covering its architecture, high‑availability replication strategies, multi‑link data flow, synchronous and asynchronous replication, performance optimizations, data export pipelines, and future development plans for the distributed NoSQL database.
The article recounts a GitLab production database deletion caused by a mistaken command, analyzes why the backup mechanisms failed, and offers technical and cultural recommendations—including automation, proper replication, and transparent post‑mortems—to build more reliable, high‑availability systems.
The article evaluates storage options for shared collections across multiple machines, explains why Redis 3.2 meets high‑availability, persistence, and data‑structure needs, and details the chosen deployment using master‑slave replication, Sentinel clusters, and supporting scripts.
The article recaps a MySQL 8.0 optimizer meetup where experts discussed version naming, enterprise vs community edition differences, character‑set choices, storage‑engine evolution, hint usage, sharding strategies, high‑availability architectures, market position, and upcoming feature requests from the community.
This article examines the performance challenges of a 700‑node Redis Cluster used by Youku, analyzes bandwidth and latency impacts of cluster communication, and presents practical tuning methods—including adjusting cluster‑node‑timeout, reducing replicas, disabling AOF, limiting cluster‑nodes commands, and tuning the hz parameter—to improve throughput and stability in massive Redis deployments.
The article presents a business‑oriented, three‑layer high‑availability architecture for a large‑scale game access platform, detailing measurable goals, client‑side retry with HTTP‑DNS, functional separation and degradation, multi‑region active‑active deployment, and automated, visual monitoring to achieve rapid fault detection, isolation, and recovery.
The article describes the high‑availability, high‑concurrency backend architecture of Weibo's paid reading and tipping platform, covering layered design, database sharding, asynchronous processing, monitoring, idempotency, distributed transaction handling, and security measures for a large‑scale internet‑finance system.
This article details Didi’s Passport authentication system architecture, describing how language migration, service decomposition, flexible ticket and SMS code designs, multi‑region active‑active deployment, an independent Argus access‑control layer, and interface splitting together achieve high availability and low latency under extreme traffic peaks.
This article explains how WeChat’s seqsvr service generates trillions of per‑user sequence numbers with sub‑millisecond latency, detailing its core architecture, pre‑allocation and section‑sharing strategies, engineering implementation with StoreSvr and AllocSvr, and the evolution of its disaster‑recovery designs from primary‑backup to embedded routing tables.
This article chronicles Meituan's payment channel gateway evolution—detailing early usable stages, subsequent availability improvements, and the implementation of a flexible, fault‑tolerant architecture that achieved 99.99% API uptime and record‑high transaction throughput.
This article shares VIPShop's extensive production experience with Redis Cluster, covering use cases, storage architecture evolution, detailed best‑practice guidelines, common pitfalls, operational automation, monitoring strategies, and useful open‑source tools for large‑scale deployments.
LeTV upgraded its payment architecture in 2015 by sharding databases, designing a Snowflake‑based globally unique order ID, implementing asynchronous replication for eventual consistency, building high‑availability master‑slave clusters with LVS and KeepAlive, tiering data caches, and adding a coarse‑fine traffic pipeline to reliably handle up to 100,000 orders per second.
The article details how LeTV upgraded its payment platform in 2015 to handle up to 100,000 orders per second by implementing database sharding based on user IDs, a Snowflake‑style globally unique order ID, asynchronous consistency via message queues, multi‑level data caching, and high‑availability architectures for both master‑slave and load‑balanced deployments.
This article explains how LeTV's payment platform handled a hundred‑fold surge in traffic by redesigning its architecture with database sharding, a custom order‑ID scheme, asynchronous consistency, high‑availability clustering, data tiering, and a coarse‑fine request pipeline to sustain up to 100,000 orders per second.
This guide explains why the official Redis Cluster tools lack password support, outlines the security risks of an unauthenticated cluster, and introduces a custom management utility that adds password authentication, automates slot migration, and simplifies adding or removing nodes, complete with step‑by‑step testing procedures.
This article shares practical design principles for building scalable read services, covering stateless architecture, data closed‑loop processing, multi‑layer caching strategies, concurrency optimization, degradation switches, rate limiting, traffic switching, and other operational best practices.
This guide explains the fundamental concepts and layered architecture of high‑availability clusters, details the software components for each layer, compares RHEL/CentOS solutions, and provides step‑by‑step instructions for configuring heartbeat2 with haresource, including node preparation, authentication, resource definitions, and service failover.
The article shares a former Google SRE’s insights on building high‑availability systems, explaining key factors such as MTBF and MTTR, redundancy strategies like N+2, change‑management practices, and practical tips for reliability engineering and operations.
The article presents a pattern‑based catalog of performance‑optimization techniques—such as horizontal and vertical partitioning, constant‑variable separation, locality, and sandboxing—illustrated with Meituan case studies, explaining motivations, trade‑offs, and how each pattern reduces latency, boosts throughput, and enhances availability in high‑throughput backend systems.
This article explains what split‑brain is in high‑availability systems, compares arbitration and fencing methods, evaluates client‑routing options without fencing devices, discusses data‑loss risks during failover for PostgreSQL and MySQL, and provides concrete implementation guidance using Pacemaker and Corosync.
The article chronicles how 58.com’s website architecture evolved through multiple growth stages—from a tiny single‑machine setup to a distributed, service‑oriented platform—by addressing scaling bottlenecks with technologies such as LAMP, read/write separation, vertical splitting, caching, and automated deployment.
This article shares Snowball's (Xueqiu) high‑availability architecture, performance optimizations, and scaling strategies—including hybrid cloud migration, service decomposition, in‑memory caching, and metric‑driven monitoring—implemented to handle massive traffic spikes and operational challenges during a volatile stock market period.
This article explains practical techniques for designing high‑availability and scalable systems by addressing entry, business, cache, and database layers, offering concrete solutions such as keepalived, stateless services, cache partitioning, and replication strategies to handle rapid user growth without service disruption.
The article outlines a Linux server architecture that mounts a read‑only root filesystem over the network from a centrally managed, DRBD‑replicated control node with Heartbeat failover, providing real‑time updates, high security (even root cannot modify), and automatic migration via virtual IP.