The article reviews eight expert presentations from the 2015 SDCC Database Practice Forum, covering distributed database architectures, performance tuning, high‑availability solutions, and practical case studies from leading Chinese internet companies.
The article presents the Binlog Server, a component that replaces intermediate masters in MySQL replication topologies to reduce network saturation, simplify disaster recovery, and improve high‑availability while supporting large numbers of slaves across remote sites.
This article explores the importance of database clustering in modern information systems, outlines the challenges of performance, availability, and scalability, and compares Share‑Disk and Share‑Nothing architectures along with their advantages, drawbacks, and real‑world implementations.
During the Chinese New Year, Tencent Cloud handled billions of WeChat red‑envelope transactions by employing multi‑region load balancing, disaster‑recovery architectures, database sharding, and high‑throughput caching to ensure seamless, high‑availability service for millions of concurrent users.
This article outlines essential design principles for large‑scale web architectures—including availability, performance, reliability, scalability, manageability and cost—and demonstrates their application through a detailed image‑hosting service example, covering services, redundancy, partitioning, caching, proxies, indexing, load balancing, and queuing to achieve efficient, scalable data access.
This article shares practical insights on achieving high availability by understanding goals, decomposing requirements, designing resilient architectures, ensuring operability, testing rigorously, and reducing release risk, illustrated through the multi‑stage evolution of a transaction system.
The article outlines the design requirements, sharding strategies, capacity planning, cost trade‑offs, and indexing techniques for building a highly available, scalable distributed storage solution for Weibo, focusing on storage‑layer decisions without involving caching or ID generation.
This article outlines Meipai’s evolution into a billion‑user short‑video platform, detailing its high‑availability, scalable architecture, service discovery via etcd, data storage challenges, CDN and cloud‑storage redundancy, fault‑tolerance mechanisms, and future directions such as H.265 adoption and P2P‑CDN hybrid delivery.
This technical session covers Oracle RAC high‑availability best practices, installation steps, daily operational commands, detailed case studies of auto‑start checks, version‑mix issues, addNode failures, network heartbeat problems, and client connection errors, plus a concise Q&A on uninstall, SCAN vs VIP, and split‑brain detection.
This article shares the architecture, design principles, challenges, and performance‑optimizing solutions behind a ten‑hundred‑thousand‑scale server monitoring system, covering data collection agents, distributed pipelines, real‑time alerts, high throughput, multi‑platform support, and practical lessons learned.
The article details Weibo's journey in building a multi‑data‑center active‑active architecture, covering its evolution, technical challenges such as latency and data synchronization, the adopted MCQ‑based messaging solution, operational best practices, and future directions for high‑availability deployments.
This article explains MySQL replication fundamentals, detailing master‑slave and multi‑master architectures, thread roles, configuration parameters, read‑write splitting, multi‑source setups, and advanced scenarios such as multi‑level and circular replication, while highlighting common pitfalls and performance considerations.
Facing up to 1.6‑1.7 billion daily requests, Momo’s tech director explains how the company built a highly available, low‑latency communication protocol and distributed infrastructure—leveraging virtualization, OpenStack, and cloud servers—to overcome weak mobile networks and serve its massive social‑gaming user base.
The article explains 58.com’s service‑oriented architecture that combines dual‑master MySQL replication, a standby database, and Redis caching to provide high‑availability read/write operations, outlines their scaling process, and details a four‑step cache‑consistency strategy.
This article describes JD’s unified service architecture for the product detail page that handled tens of billions of requests during Double Eleven, detailing the multi‑level caching strategy, Nginx+Lua access layer, service isolation, degradation mechanisms, and front‑end logic offloading.
This article walks through implementing web high availability and static‑dynamic content separation using HAProxy combined with Keepalived, covering load‑balancing concepts, VRRP basics, step‑by‑step configuration of time sync, hostnames, SSH trust, installing required packages, and testing failover scenarios.
This article explains the design, storage mechanisms, high‑availability architecture, scaling strategies, multi‑data‑center disaster recovery, operational management, and future plans of Taobao’s distributed file system (TFS), a highly available and scalable storage solution for massive unstructured data.
Taobao’s File System (TFS) is a highly available, high‑performance distributed storage solution built on Linux servers, featuring name‑server and data‑server clusters, block‑level replication, HA mechanisms, client caching, seamless scaling, multi‑data‑center disaster recovery, and open‑source support for C++, Java, and Nginx integration.
The article describes how the limitations of an in‑memory NoSQL HOLD platform led to the creation of TDSQL, a distributed MySQL‑based SQL system featuring ZooKeeper‑coordinated Scheduler, Agent, and Gateway modules, automatic cross‑IDC disaster recovery, transparent horizontal scaling, strong synchronous replication, and future integration with container technologies.
The article chronicles how 58.com’s web architecture evolved from a tiny, single‑machine setup to a multi‑layer, Java‑based, highly available service‑oriented platform, detailing the technical decisions, scaling challenges, and automation practices adopted at each traffic milestone.
This article outlines the UIOC (Urgent Incident Office Center) process, detailing a six‑step workflow, multi‑team collaboration tactics, common troubleshooting methods, and pitfalls to avoid, helping operations teams achieve 99.99% availability while handling emergencies efficiently.
Tencent’s operations team explains how its SET‑based NoSQL clusters deliver ultra‑low latency, high availability, and seamless disaster recovery for billions of users, detailing deployment models, synchronization mechanisms, cost‑saving techniques, and the Data‑as‑Service approach that underpins its massive social platforms.
This article explains how TDSQL transforms MySQL into a distributed, high‑availability SQL system by addressing NoSQL limitations, introducing a Scheduler‑Agent‑Gateway architecture, automatic scaling, sharding, robust disaster‑recovery mechanisms, and future integration with container technologies.
This article details the evolution and redesign of JD.com’s product detail page architecture, describing the transition from static HTML generation to a dynamic, high‑performance, multi‑datacenter system built on key‑value storage, Nginx + Lua, asynchronous processing, multi‑level caching, and robust scaling and reliability strategies.
This article describes how JD.com redesigned its product detail page system from a static, cache‑heavy architecture to a fully dynamic, multi‑level cached service using Nginx+Lua, JIMDB, and asynchronous workers, addressing scalability, performance, and high‑availability challenges for billions of daily page views.
The article analyzes the use of a master/slave architecture for distributed caching, explains why two clusters, CAS, and proxy are employed, discusses consistency and availability challenges, and evaluates possible mitigation strategies for cache failures.
DRBD (Distributed Replicated Block Device) is a software‑based, network‑driven block replication solution that mirrors disks, partitions, or logical volumes across servers in real time, offering synchronous and asynchronous modes, transparent failover, and a middle‑layer between the filesystem and physical storage.
The article explains how distributed systems split a task into multiple subtasks across separate servers to reduce execution time, while clusters replicate the same service on many servers to increase throughput, highlighting their complementary roles in scalability and high availability.
This article explains how Keepalived automatically monitors web servers at the IP, TCP, and application layers, removes unhealthy nodes, and reintegrates them once recovered, thereby maintaining high availability and reducing manual maintenance in complex server clusters.
When read traffic overwhelms a single MySQL master, cascading replication and dual-master setups can distribute slave load, reduce replication lag, and simplify failover, offering a scalable solution that balances read/write pressure across multiple replication layers.
An in‑depth look at Weibo’s evolution to its third‑generation backend system, detailing the orthogonal decomposition model, three‑tier horizontal layering, key middleware such as MCQ, Motan RPC, SSDCache, and the WatchMan tracing platform that together enable high‑availability, massive concurrency, and low‑latency services for billions of users.
This article presents Sogou's design for a highly available, high‑performance, and horizontally scalable business platform, illustrating key architectural components and scalability strategies through a series of diagrams.
This article compiles recent high‑availability architecture discussions covering plugin‑based system design, simple kanban tools, independent scheduling services, challenges of managing 60‑billion‑row tables, and the trade‑offs between UUIDs and custom distributed ID generators, offering practical insights for backend engineers.
This article introduces MySQL Cluster’s share‑nothing architecture, explains the NDB storage engine’s advantages and drawbacks, describes the management, data, and API node roles, and provides a step‑by‑step configuration and deployment tutorial with command‑line examples.
This article explains the motivations behind key‑value stores, compares Redis with the newly created QDB, and details the architecture, dynamic resharding, high‑availability mechanisms, and future improvements of the distributed database solution RebornDB.
The article details Uber senior engineer Zhao Lei’s presentation on building a highly available messaging platform, covering single‑point failure mitigation, sharding approaches, large‑scale outage handling, cross‑region failover, and the practical engineering practices and protocols used to keep billions of users online.
Keepalived, built on LVS, automatically monitors service nodes, isolates failed machines, and performs seamless failover between load balancers using VRRPv2, allowing web servers to be added or removed without manual intervention, thus ensuring high availability and efficient load distribution.
This article presents an in‑depth overview of Codis and its next‑generation project RebornDB, covering Redis, Redis Cluster, the proxy‑based architecture, consistency trade‑offs, production deployment experiences, operational pitfalls, and broader perspectives on distributed databases and architectures.
This article examines WhatsApp’s high‑reliability architecture that supports 450 million users, detailing its Erlang‑based backend, hardware choices, scaling techniques, performance metrics, monitoring tools, and lessons learned from achieving up to two million concurrent connections on a single server.
The article explains why Kafka introduced high availability starting with version 0.8, detailing the need for data replication and leader election, describing replica distribution algorithms, replication mechanics, ISR handling, ZooKeeper structures, and the broker failover process to ensure fault‑tolerant streaming.
The 2015 Beijing QCon highlighted four technical talks covering asynchronous processing in distributed systems, the DRC data‑replication infrastructure, minute‑level high‑availability fault recovery, and cloud‑era database operations, illustrating Alibaba's approaches to scalability and reliability in modern cloud platforms.
This article examines common NoSQL key‑value stores such as Memcached and Redis, compares their strengths and limitations, and proposes a distributed architecture with routing, storage, management, and migration nodes that achieves high availability, automatic fault‑tolerance, load balancing, and elastic scaling.
This article explains Hadoop 2.0's High Availability architecture, comparing the NFS and Quorum Journal Manager methods, detailing their principles, failover mechanisms, and practical tips for reliable NameNode redundancy in big‑data deployments.
This article compares Redis with MySQL, outlines their similarities and differences, examines Redis alongside Memcached, EhCache, and OSCache, and proposes a simple high‑availability architecture for Redis, highlighting performance, data model, scalability, and operational considerations.
This article explains what a Linux cluster is, contrasts it with distributed systems, outlines its two main characteristics—scalability and high availability—along with essential capabilities like load balancing and error recovery, and details common cluster types such as high‑availability, load‑balancing, and high‑performance computing clusters.
This comprehensive tutorial walks you through Redis Cluster fundamentals, including installation, hash slot sharding, node replication, fault tolerance, configuration files, cluster creation commands, and client testing, all without delving into complex distributed theory.
At Baidu’s 49th Technical Salon, Cheng Yishi explained how the company revamped its MooseFS and Redis systems by adding a Shadow Master to split reads from writes, introducing Slave nodes for failover, and deploying a Redis proxy middleware, thereby dramatically improving performance, scalability, and high‑availability for critical services.
