This article explains the stability challenges of large‑scale Kubernetes clusters, outlines ACK's high‑availability architecture and component optimizations, and details product features such as Prometheus, AIOps and managed node pools that together ensure reliable, performant cloud‑native workloads.
Taobao’s marketing technology team built a platform‑centric architecture that separates merchant acquisition, ad placement, benefits, and scene construction, enabling 80‑90% feature reuse while tackling challenges such as massive merchant onboarding, real‑time rule validation, price consistency, ultra‑high‑concurrency lottery draws, low‑end device rendering, and AI‑driven asset creation.
This article provides an extensive overview of software architecture, covering its definition, history, core concepts, design principles, complexity sources, design process, performance, high availability, scalability, and practical implementation techniques for large‑scale web systems.
This article presents five expansion strategies—shutdown, write‑stop, log‑based, dual‑write, and smooth 2N—detailing step‑by‑step procedures for MariaDB installation, master‑master replication, dynamic data‑source configuration, and Keepalived high‑availability setup, enabling seamless horizontal scaling and minimal service disruption for large‑scale databases.
Understanding the differences between system availability, reliability, and stability is essential for building resilient services; this guide explains each concept, illustrates their distinctions with examples, and outlines practical strategies such as rate limiting, anti‑scraping, timeout settings, system inspections, and fault post‑mortems to reduce failures and downtime.
An unprecedented Alibaba Cloud outage that crippled services like Aliyun Drive, Taobao, and DingTalk highlighted the critical need for high‑availability, multi‑region architectures, prompting a detailed look at the incident timeline, affected products, and practical design lessons for ensuring resilient cloud deployments.
This article explains how Redis evolved from a simple cache to a high‑performance distributed data store, covering its architecture, persistence models, scalability, high‑availability features, complex data structures, and the trade‑offs of using it as a primary database versus a traditional relational system.
This document outlines the business scope, value, overall and real‑time data layer architecture, design advantages, data model, extensibility, and future challenges of the order system, emphasizing decoupling, high availability, scalability, and cost control.
This article explains the principles of disaster recovery for MySQL, covering RTO/RPO metrics, national backup level standards, common master‑slave topologies, a comparative analysis of high‑availability solutions, and a detailed three‑center multi‑region replication design with code patches to avoid replication loops.
This article outlines a systematic approach to ensuring high availability for e‑commerce mega‑promotion events, covering historical context, business model analysis, goal setting, strategic planning, tactical execution, and growth, with detailed evaluation of marketing, transaction, fulfillment, and monitoring processes.
The article details JD Logistics' order system redesign using a four‑layer transaction architecture, describing its decoupled backend, unified data model, high‑availability components such as CQRS, Redis, JMQ, HBase, and Elasticsearch, and outlines design advantages, extensible data modeling, future challenges, and overall performance outcomes.
This article explains the ALUA (Asymmetric Logical Unit Access) multipath model, compares it with other storage path mechanisms, describes its operation in dual‑active environments, outlines key features such as path states and failover, and reviews native ALUA support across major operating systems.
LApiGateway is Huolala's custom Java-based microservice gateway built on Spring Cloud Gateway, featuring service discovery via Consul, centralized configuration, a rich plugin system, DSL-driven routing, high‑availability designs like physical and service isolation, gray‑scale migration, traffic pre‑warming, and adaptive load balancing to ensure stable, efficient API management.
TuGraph-DB v4.0, the open‑source graph database from Ant Group, introduces ISO GQL compliance, enterprise‑grade high availability with RAFT‑based leader election, and an integrated graph learning engine compatible with DGL and PyG, enhancing query capabilities, scalability, and AI‑driven analytics.
This article details the design of a decoupled, high‑availability order system, covering business scope, value propositions, layered architecture, real‑time data layer, read/write separation, caching, messaging, search, multi‑tenant support, data security, and future challenges such as personalized queries and cost‑effective scaling.
This article details the architectural evolution, high‑availability strategies, fault‑monitoring mechanisms, and performance optimizations of AutoHome's enterprise SMS platform, covering its migration from .Net to Java, service decomposition with Kafka, multi‑datacenter deployment, and operational safeguards for large‑scale events.
This article explains how to build robust, highly available cloud‑native applications on Alibaba Cloud Container Service for Kubernetes (ACK) by covering architecture principles, multi‑zone cluster design, Kubernetes HA features such as topology spread constraints and pod anti‑affinity, storage strategies, load‑balancing, virtual nodes, health probes, monitoring, and multi‑cluster deployment patterns.
The article examines the driving forces behind database innovation, emphasizing the role of inherent shortcomings, AI integration, and the emergence of third‑generation distributed databases that aim for minimal usability, controllable latency high availability, and 100% data correctness.
This article provides a comprehensive technical walkthrough of Redis, covering its core concepts, data structures, performance tricks, caching pitfalls, persistence options, high‑availability architectures, distributed locking mechanisms, and consistency strategies, all illustrated with concrete examples and code snippets.
This article explains how to build a dual‑stream real‑time data pipeline for big‑data applications, defines construction standards, and details a three‑step high‑fidelity load‑testing process that ensures stability and high availability during peak promotional periods.
This article provides a comprehensive technical overview of NewSQL concepts and TiDB, covering its origins, core features, distributed architecture, high‑availability design, MySQL compatibility, unsupported MySQL functionalities, configuration defaults, and real‑world application scenarios for both OLTP and OLAP workloads.
The article outlines the design and evolution of an enterprise‑level unified push notification service, detailing its modular to service‑oriented architecture, multi‑channel support, high‑performance non‑functional requirements, and the comprehensive components such as clients, notification, template, distribution, priority queues, adapters, analytics, and database layers.
This article details Huolala's big‑data architecture and the practical measures—ranging from background analysis and stability challenges to case studies, discovery mechanisms, capacity planning, high‑availability, and automation—that the company employs to guarantee Doris's reliability and performance across its rapidly growing logistics platform.
This article introduces Redis as an open‑source in‑memory key‑value store, explains its data‑structure server nature, outlines common deployment options—including single instance, high‑availability, Sentinel, and Cluster—describes replication mechanisms, and details persistence models such as RDB, AOF, and hybrid approaches.
This article explains how MySQL InnoDB Cluster 8.1 introduces read‑only replica instances, shows step‑by‑step commands to create and configure them, describes their failover behavior, routing options with MySQL Router, health‑check isolation, replication‑lag handling, and how to hide replicas from traffic.
This article outlines a comprehensive framework for preparing e‑commerce platforms for major sales events, covering the history of promotions, business models, system chain segmentation, stability goals, strategic planning, tactical measures, growth promotion, and reference resources to ensure high availability and reliable user experience.
This article outlines key strategies and Python tools for server monitoring, including defining metrics, utilizing libraries like psutil and requests, log analysis, load testing with Locust and PyTest, and implementing automated alerts for high availability.
This article thoroughly examines MySQL replication, detailing binlog formats, event types, replication workflows, semi‑synchronous and parallel replication techniques, performance benchmarks, and practical implementation steps such as fake‑slave registration and connection‑pool enhancements, while illustrating each concept with concrete examples and code snippets.
The article explains what high availability really means, why it’s essential, outlines six core design principles, compares cloud and on‑premise HA, highlights common pitfalls, and provides a practical multi‑AZ architecture example to help engineers build more reliable systems.
This article details the design and implementation of a highly available, high‑performance membership system serving over a billion users, covering dual‑center Elasticsearch clusters, traffic‑isolated three‑cluster ES architecture, Redis dual‑center caching, MySQL partitioned clusters, migration strategies, and refined flow‑control and degradation mechanisms.
This guide explains how to design a Kubernetes‑based architecture for a large‑scale online store, covering component containerization, auto‑scaling mechanisms, high‑availability deployment, continuous delivery, and monitoring integration to handle traffic spikes reliably.
This comprehensive guide walks you through the challenges of monolithic deployments, explains core Nginx concepts, shows step‑by‑step installation, configures reverse proxy, static‑dynamic separation, compression, buffering, caching, security features, SSL, high‑availability with keepalived, and essential performance tuning for production‑grade servers.
This article details the architectural redesign of QQ Music's comment platform—migrating to MongoDB, introducing threaded comments, and employing caching and message‑queue decoupling—to handle massive read/write spikes during celebrity live‑drop events while maintaining high availability and performance.
QQ Music’s comment system was re‑engineered with a MongoDB backend, cache layer, asynchronous writes, split read/write services, priority queues and rate‑limiting, enabling it to endure celebrity‑driven traffic spikes, maintain data consistency, and deliver high‑availability, low‑latency user experiences.
This article details the end‑to‑end high‑availability architecture—including dual‑center Elasticsearch clusters, Redis caching with distributed locks, and a dual‑center MySQL partitioned setup—that enables a membership platform serving billions of users to sustain massive traffic while ensuring data consistency and rapid recovery.
This article explains Didi's self‑developed DCDR system that replicates Elasticsearch indices across data‑center clusters, detailing its design goals, core mechanisms, chain construction, historical data recovery, real‑time sync, and data‑quality validation to ensure high availability and strong consistency.
This document outlines the standards, evaluation dimensions, and implementation process for dual‑stream construction in big‑data pipelines, describes high‑fidelity pressure‑testing methods and objectives, and provides migration procedures for business units not participating in the tests.
This article explains how RaftKeeper leverages the Raft consensus algorithm to create a high‑availability, high‑performance ClickHouse cluster across multiple data centers, covering project background, architecture, core features, performance optimizations, and real‑world deployment results.
This article reflects on years of designing large‑scale backend systems at Tencent, discussing how to define clear architecture boundaries, ensure high availability, integrate diverse technologies, and use observability and monitoring to continuously evolve and improve massive service architectures.
Tengine-Ingress, Alibaba’s cloud‑native ingress gateway built on Tengine‑Proxy, replaces the legacy Tengine gateway by delivering dynamic, loss‑less configuration updates, high‑availability gray‑release mechanisms, global consistency checks, and significant performance gains in TLS handshake latency, CPU usage, and memory consumption across large‑scale deployments.
This article explains the VRRP protocol’s core concepts, state machine, election process, and multi‑master HA mode, provides step‑by‑step Linux router configuration examples—including group creation, priority, interface tracking, preempt mode, timers, and learning—plus an overview of Keepalived’s architecture and split‑brain mitigation strategies.
The article describes how a membership system serving billions of users across multiple platforms achieves high performance and high availability through dual‑center Elasticsearch clusters, traffic‑isolated three‑cluster ES architecture, Redis caching with distributed locks, dual‑center MySQL partitioning, and fine‑grained flow‑control and degradation strategies.
This article walks through Redis's evolution from a simple single‑instance cache to a highly available, high‑performance cluster, explaining persistence mechanisms (RDB, AOF, hybrid), master‑slave replication, Sentinel automatic failover, and sharding strategies with concrete examples and trade‑offs.
Ximalaya’s KV storage progressed from a simple Redis master‑slave setup to client‑side sharding, then adopted Codis clustering for elastic scaling, integrated Pika’s disk‑based store with cold‑hot separation, introduced KV‑blob separation, fast‑slow command pools, second‑level expansion, ehash fields, large‑key circuit breaking, multi‑active data‑center replication, and now targets cloud‑native deployment, advanced features, and AI‑driven operations.
This article explores essential software engineering practices—including the DRY principle, SOLID design principles, common design patterns, high‑availability architecture, automation, effective communication, and career development—offering concrete examples, code snippets, and actionable advice to help developers write cleaner, more maintainable, and scalable code.
The article analyzes the importance of the 618 sales event, identifies factors that threaten system stability such as traffic spikes, massive data, complex scenarios, long delivery chains and low tolerance, and proposes comprehensive application, storage, and operational measures—including unitization, monitoring, logging, fast‑fail, rate‑limiting, degradation, database and cache designs, and emergency processes—to guarantee reliable service during the promotion.
Drawing on the book 'From Zero to Architecture' and personal experience, this article outlines practical design methods that define core concepts, address performance, availability and scalability complexities, and detail patterns for storage and compute optimization, fault‑tolerant interfaces, modular architectures, and evolutionary refactoring to build sustainable high‑quality systems.
This article explains MySQL master‑slave architecture, why it’s used, the replication process, consistency challenges, causes of replication lag, and practical strategies—including binlog formats, mixed mode, monitoring, caching, and failover setups—to optimize performance and ensure high availability.
This article examines RocketMQ's high‑availability evolution—from early master‑slave and Raft‑based designs to the v5 DLedger fusion model—detailing replica groups, data sharding, election mechanisms, replication strategies, metric trade‑offs, log‑divergence handling, controller roles, heartbeat optimizations, and comparisons with Kafka and Pulsar, all illustrated with diagrams and code snippets.
This article explains how Redis Sentinel provides automated failover, details the replication process that keeps master and slave data synchronized, and compares the roles of master‑slave replication, Sentinel, and Redis Cluster in achieving high availability and horizontal scalability.
A recent Redis deployment faced memory expansion, a master‑slave switch, and unexpected data loss when the new master entered read‑only mode, prompting a deep dive into sentinel behavior, maxmemory settings, and replica‑ignore‑maxmemory nuances to prevent similar failures.
This article details the design and implementation of a highly available, high‑performance membership platform serving over a billion users, covering Elasticsearch dual‑center clusters, traffic‑isolated clusters, deep ES optimizations, Redis caching strategies, MySQL dual‑center partitioning, seamless migration, and fine‑grained flow‑control and degradation mechanisms.
This article explains the concept of high availability, outlines the challenges of collaborative delivery, architectural design, coding practices, secure release, and deployment operations, and provides concrete steps, process standards, emergency plans, and self‑check tools to ensure reliable, fault‑tolerant software systems.
This article details the design and implementation of a highly available, high‑performance membership system that serves over a billion users, covering Elasticsearch dual‑center HA, traffic‑isolated clusters, Redis caching, MySQL dual‑center partitioning, seamless migration, and refined flow‑control and degradation strategies.
A senior Tencent Cloud backend engineer outlines practical best‑practice guidelines—applying DRY and SOLID principles, leveraging common design patterns, designing high‑availability architectures, automating workflows, prioritizing value‑driven development, fostering clear communication, ensuring reliability, and encouraging continuous learning—to write clean, maintainable, and resilient backend systems.
This article examines why traditional single‑node databases struggle with growing data volumes, outlines the three main distributed‑database architectures, compares their trade‑offs in availability, consistency, scalability and operational complexity, and offers practical criteria for deciding whether a distributed solution is truly needed.
This guide explains how to design and deploy a highly available, scalable e‑commerce platform on Kubernetes by containerizing services, planning clusters, configuring replication, load balancing, persistent storage, monitoring, security, CI/CD pipelines, and provides complete YAML examples for frontend, backend, and database components.
This guide outlines practical methods to avoid split‑brain incidents in production HA clusters, including dual‑cable heartbeats, arbitration mechanisms, monitoring alerts, disk‑locking techniques, and a detailed keepalived‑based script for automated detection and recovery.
This article presents a comprehensive engineering case study of a high‑traffic membership system, detailing the dual‑center Elasticsearch high‑availability design, traffic‑isolated three‑cluster ES architecture, Redis caching strategy, dual‑center MySQL partitioning and migration plan, abnormal member relationship governance, and future fine‑grained flow‑control and downgrade policies.
This article outlines a comprehensive Redis training program covering fundamentals, distributed lock implementation, high‑availability mechanisms, clustering, persistence strategies, and practical projects such as Bloom filter integration and flash‑sale systems, providing learners with the knowledge to master advanced Redis usage.
Meituan’s high‑availability database system, built on a multi‑region Raft‑group architecture, addresses rapid instance growth and stringent availability by deploying three‑node HA cores, micro‑services, and MGR clusters with AZ‑ and region‑level disaster recovery, while employing multi‑channel fault detection, weighted election, and semi‑synchronous consistency mechanisms, and outlines future moves toward decentralized proxies and fully clustered designs.
This article details the design and implementation of a high‑performance, highly available membership platform serving billions of users, covering dual‑center Elasticsearch clusters, traffic‑isolated three‑cluster ES architecture, Redis caching strategies, MySQL dual‑center partitioning, seamless migration, and fine‑grained flow‑control and degradation mechanisms.
This article details HuoLa La's journey of designing, implementing, and evolving a hybrid‑cloud self‑built database middleware that unifies multi‑cloud environments, achieves up to 1024× MySQL horizontal scaling, and addresses challenges such as multi‑language stacks, high availability, SQL governance, and multi‑AZ deployment.
This comprehensive guide covers why Redis is fast, its underlying data structures, single‑threaded and epoll models, cache eviction policies, persistence mechanisms, high‑availability architecture, performance bottlenecks, distributed locking, cache avalanche/penetration strategies, data skew handling, and bitmap applications, providing essential knowledge for interview preparation.
This article provides a comprehensive overview of Kafka, covering its core value as a message queue, fundamental concepts, cluster architecture, log storage mechanisms, zero‑copy data transfer, high‑throughput and high‑availability design, consumer group behavior, rebalance strategies, and practical operational commands for managing topics, partitions, and offsets.
This article explains Kafka's cross‑data‑center high‑availability options, compares stretched and connected cluster designs, outlines typical failure scenarios, and reviews both community and commercial replication solutions, helping architects choose the most suitable deployment for their specific requirements.
This article explains MySQL replication, covering its background, binlog fundamentals, replication formats, positioning methods, asynchronous and semi‑synchronous workflows, parallel replication techniques, and real‑world implementation details for high availability and data synchronization.
This technical guide explains how to scale a sharded database horizontally by introducing five expansion schemes—including shutdown, write‑stop, log‑based, dual‑write, and smooth 2N approaches—covers MariaDB installation, master‑master replication setup, dynamic data‑source configuration with ShardingJDBC, and detailed Keepalived high‑availability configuration for seamless service continuity.
This article details the design and implementation of a high‑availability, billion‑scale membership system, covering Elasticsearch dual‑center clusters, traffic‑isolated architectures, deep ES optimizations, Redis caching strategies, MySQL migration with dual‑center partitioning, abnormal member relationship handling, and future fine‑grained flow‑control and degradation plans.
This article explains why native Prometheus HA solutions fall short for large, multi‑region clusters and shows how to use Thanos components—including sidecar, query, store gateway, and compactor—to achieve long‑term storage, unlimited scaling, a global view, and non‑intrusive integration with existing Prometheus deployments.
The article details vivo’s transition from a monolithic mall to a micro‑service transaction platform, outlining a multi‑tenant architecture with ShardingSphere‑sharded MySQL, Snowflake IDs, Elasticsearch search, configurable state machines, generic delayed tasks, Seata and local‑message distributed transactions, plus high‑availability safeguards, emphasizing pragmatic solution selection.
The article by Tencent backend expert Lv Yuanfang explains how to design scalable mobile‑internet backend architectures and push services by defining clear protocol boundaries, aligning system components with team organization through a conversion‑layer service, and implementing comprehensive feedback loops—including health metrics, monitoring, and data‑driven analysis—to ensure high availability and low coupling.
This article explains MySQL replication’s background, binlog formats, event types, positioning methods, asynchronous and semi‑synchronous workflows, parallel replication techniques, and real‑world deployment strategies such as HA components, middleware, remote binlog copying, and data‑transfer services, providing a comprehensive guide for building highly available and scalable MySQL infrastructures.
This article explains MySQL master‑slave replication, covering its architecture, binlog‑based replication process, causes and mitigation of replication lag, and strategies for master‑slave failover, helping readers grasp why and how to use replication for read/write separation, high availability, and backup.
ByteHouse evolved its real‑time import pipeline from a community ClickHouse architecture to a custom HaKafka engine and a cloud‑native design, addressing node failures, read‑write conflicts, scaling costs, and latency by introducing two‑level concurrency, memory tables, exactly‑once semantics, and robust fault‑tolerance.
This article details the motivation, architectural evolution, and technical implementations of ByteHouse's real‑time ingestion pipeline, covering internal business requirements, distributed‑system challenges, the custom HaKafka engine, memory‑table optimizations, and the transition to a cloud‑native design that delivers high availability, low‑latency, and exactly‑once semantics.
This guide explains how to enable cross‑cluster pod communication in Kubernetes using Kube‑OVN's OVN‑IC feature, covering prerequisites, single‑node and high‑availability database deployment, automatic and manual route configuration, and cleanup procedures with concrete Docker/Containerd commands and ConfigMap examples.
This article explains how to expand a sharded database from three to four nodes, compares five migration schemes—including stop‑service, stop‑write, log‑based, dual‑write, and smooth 2N approaches—and provides step‑by‑step instructions for MariaDB installation, master‑slave configuration, Keepalived high‑availability setup, and dynamic data‑source integration using ShardingJDBC.
This article introduces an online practice of cluster rate limiting based on Sentinel, providing a high-availability solution for Sentinel cluster rate limiting and implementing automatic allocation and failover of Token servers.
The article details how a multi‑layer load‑balancing platform (VGW) was designed—combining 7‑layer Nginx, 4‑layer LVS with FULLNAT, and 3‑layer network devices—to achieve business reliability, fault isolation via BGP‑announced VIPs, and high‑throughput performance using DPDK, while providing redundancy at server, link, and cluster levels.
This article explains the evolution, architecture, and high‑availability solutions of ByteDance’s Abase KV storage system, detailing its multi‑write design, leader‑less approach, multi‑region deployment, consistency mechanisms, performance optimizations, and real‑world metrics that support billions of requests per second.
The article explains how system failures like bugs, security breaches, and cloud outages can cripple businesses, and outlines the concepts of fault tolerance and disaster recovery as essential components of high‑availability architectures to ensure continuous service and protect revenue.
This article explains the concept of high availability, outlines the challenges of achieving it in complex software delivery chains, and provides practical guidance on improving collaboration efficiency, establishing process standards, designing robust architecture, implementing disciplined coding, executing safe releases, and maintaining operational safeguards.
This article explains why disaster‑recovery and active‑active architectures are essential for OLAP MPP data‑warehouse clusters, outlines the specific RPO/RTO requirements for batch and real‑time workloads, and compares several data‑synchronization techniques and active‑active deployment models with their advantages and drawbacks.
The article outlines essential high‑availability techniques for internet‑scale systems, covering availability metrics, microservice modularization, database redundancy, load balancing, rate limiting, circuit breaking, isolation, retry strategies, rollback plans, stress testing, monitoring, and on‑call procedures.
The article outlines a comprehensive high‑availability architecture framework across six layers—development standards, application services, storage, product fallback, operations deployment, and emergency response—detailing design principles such as stateless services, elastic scaling, redundant storage, robust monitoring, gray releases, and chaos engineering to ensure resilient, continuously available systems.
This article explains how to set up a high‑availability Nginx service using Keepalived on two CentOS virtual machines, covering installation, configuration of keepalived, health‑check scripts, virtual IP management, and failover testing to ensure continuous service availability.
This article documents a MySQL read‑write splitting architecture, investigates an unexpected slave‑node crash, and provides a step‑by‑step guide to using Keepalived for monitoring and automatically restarting the MySQL container to achieve high availability of the replica.
This article details the background, migration options, and step‑by‑step automated procedures used by a large‑scale e‑commerce platform to safely move over 400 MySQL clusters, comparing expansion‑plus‑master‑slave switching with cascading replication and explaining the chosen fast, reliable solution.
This article provides a step‑by‑step tutorial on installing Nginx, setting up reverse proxy and various load‑balancing methods, configuring upstream directives, enabling SSL, and building high‑availability clusters using Keepalived and LVS with detailed command examples and configuration snippets.
This article details how a large‑scale membership platform achieves high performance and high availability by employing a dual‑center Elasticsearch cluster, traffic‑isolated ES clusters, deep ES optimizations, Redis caching with distributed locks, dual‑center MySQL partitioning, seamless data migration, and fine‑grained flow‑control and degradation strategies.
This article provides a comprehensive overview of Redis, covering its role as an in‑memory data‑structure server, various deployment topologies such as single instances, high‑availability, Sentinel, replication, and clustering, as well as its persistence mechanisms including RDB, AOF, and fork‑based snapshots.
This comprehensive guide walks you through Nginx fundamentals, environment setup, reverse‑proxy load balancing, static‑dynamic separation, resource compression, buffering, caching, IP whitelist/blacklist, cross‑origin handling, anti‑hotlinking, large‑file transfer, SSL configuration, high‑availability with Keepalived, and performance‑tuning techniques for production‑grade deployments.
This extensive tutorial walks through Nginx fundamentals, environment setup, reverse‑proxy load balancing, static‑dynamic separation, resource compression, buffering, proxy caching, IP black‑white listing, anti‑hotlinking, large‑file handling, SSL configuration, high‑availability with Keepalived, and key performance‑tuning techniques for production deployments.
This article analyzes common Jenkins high‑availability challenges, reviews existing industry solutions, and presents Vivo's own Jenkins Scheduler architecture—including API‑gateway, event center, scheduling algorithms, flow‑control, and callback mechanisms—demonstrating its production deployment and future container‑based evolution.
Bilibili’s Config Center evolved from the 2017 Config v1 monolith—offering unified UI, MySQL storage, and long‑polling—to the Raft‑based Paladin v2, which adds lifecycle management, tenant isolation, incremental publishing, high‑throughput caching, multi‑active deployment, validation and rich tooling, handling hundreds of thousands of configs and tens of thousands of concurrent clients with sub‑50 ms push latency while planning deeper K8s integration.
This guide walks through designing and deploying a highly available, scalable WordPress web application on JD Cloud using elastic IaaS, PAAS services, load balancers, HA groups, Docker containers, MySQL, Redis, and automated scripts to demonstrate fault‑tolerance across availability zones.
This article details Meituan's three‑stage evolution of its self‑developed Code platform—from a single‑machine service to a multi‑machine read‑write‑separated system and finally to a distributed, sharded architecture—highlighting the scalability and high‑availability challenges faced and the engineering solutions implemented.
Meituan’s home‑grown Code platform evolved from a single‑server Git service to a distributed, sharded system with multi‑active replication, using Go‑based HTTP/SSH proxies, gRPC communication, and version‑based routing to achieve horizontal scalability, high availability, and millions of daily Git operations.
This guide walks through preparing two CentOS virtual machines, installing Nginx, explaining high availability concepts, and configuring Keepalived with VRRP to achieve automatic failover and virtual IP management for a resilient Nginx service.
