0 views collected around this technical thread.
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 explains the differences between SLA, SLO, and SLI, shows how to express user expectations as concrete service level agreements, and introduces essential high‑availability metrics such as availability percentages, MTBF, MTTR, RPO, RTO, WRT, and MTD for reliable system design.
This article explains MySQL dual‑master architecture, covering dual‑master replication, master‑slave replication, master‑master with backup nodes, and ring replication, while discussing their advantages, common pitfalls such as loop replication and data inconsistency, and practical solutions to ensure high availability and data integrity.
This article explains how to build a high‑availability, million‑level concurrent architecture by combining Linux Virtual Server (LVS) for layer‑4 load balancing, Nginx for layer‑7 reverse proxy and caching, and Keepalived for VIP failover, including configuration examples and deployment modes.
This paper presents the design, implementation, and experimental evaluation of OceanBase's unitization architecture for large‑scale online map services, demonstrating superior disaster‑recovery, high‑throughput OLTP/OLAP performance, and storage efficiency compared with competing distributed databases.
This article explains the role of consensus algorithms in achieving high‑availability through redundancy and automatic failover, clarifies distributed consistency, explores the CAP theorem and its C component, and introduces the BASE theory as a practical complement for eventual consistency in modern distributed systems.
This guide explains why three servers are needed for high availability, walks through hardware and software preparation, network configuration, MySQL master‑slave replication setup, HAProxy load‑balancing, and firewall/SELinux adjustments, providing complete command‑line examples for each step.
This article explores how to build fault‑tolerant distributed systems by formalizing consensus, outlines its core properties, explains the FLP impossibility theorem, and shows how algorithms like Raft sidestep its limits through timing constraints and recovery mechanisms.
This comprehensive guide explains Redis's core architecture, the underlying implementation of its various data types, persistence mechanisms (RDB and AOF), high‑availability solutions such as replication, Sentinel and Cluster, as well as performance‑monitoring techniques and common optimization strategies.
This article explains the key Redis cluster configuration options found in redis.conf, detailing required settings such as cluster-enabled, cluster-config-file, and cluster-node-timeout, as well as optional parameters like cluster-slave-validity-factor, migration barrier, full coverage requirement, and read‑when‑down behavior.
Redis cluster relies on two ports per node, a hash‑slot based sharding scheme, a master‑slave replication model, and provides eventual consistency, making these four fundamentals essential knowledge for developers and operators to.
This article objectively compares middleware‑based sharding with NewSQL distributed databases, examining their architectural differences, transaction models, high‑availability mechanisms, scaling, SQL support, storage engines, and maturity to help practitioners decide which approach best fits their workload and operational constraints.
This article explains how RocketMQ achieves high availability and data reliability through its master‑slave broker design, covering synchronous and asynchronous replication, flush strategies, transaction messaging, automatic failover with Dledger, and read‑write separation for load balancing in distributed systems.
This article explains MySQL's replication mechanism, detailing master‑slave architecture, key threads, binlog formats (statement, row, mixed), common application scenarios such as backup, read/write splitting, and data migration, and highlights important considerations like network latency, consistency, delay, and security.
Gaode Map’s new integrated container architecture, combined with on‑demand loading, package slimming, and multi‑system/device/language support, delivers ultra‑stable, high‑availability navigation with second‑level startup, halved binary size and traffic, enabling efficient, cross‑platform mobile mapping for diverse hardware.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding solutions, examining their architectures, distributed transaction handling, high‑availability, scaling, storage engines, and ecosystem maturity, and provides guidance on selecting the appropriate approach based on consistency, growth, operational capacity, and performance requirements.
This article provides a comprehensive guide to Redis Cluster, covering its background, overall architecture, deployment steps, configuration templates, cluster creation commands, basic key‑value operations, high‑availability testing, and how to manually assign master‑slave relationships for robust distributed caching.
The article explains how fault testing—by deliberately injecting failures in a controlled environment—helps identify system weaknesses, validates post‑mortem improvements, and drives architectural optimization, thereby increasing high‑availability and resilience of modern internet services.
The article objectively compares NewSQL distributed databases with middleware‑plus‑sharding solutions, covering architectural differences, distributed transaction handling, high‑availability, scaling, SQL support, storage engines, maturity, and provides a decision‑making checklist to help engineers select the most suitable approach for their workloads.
The article describes the evolution from modular push modules to a framework‑based and finally a service‑oriented unified push platform, detailing its architecture, functional and non‑functional requirements, component responsibilities, and deployment considerations for high‑performance, scalable enterprise notification systems.