The article explains that MySQL redo log operates at the InnoDB engine layer to ensure transaction durability and crash recovery, while binlog works at the server layer to record logical changes for replication, archiving, and point‑in‑time recovery, highlighting their distinct layers, purposes, content, and write mechanisms.
The article compares PostgreSQL and MySQL, highlighting PostgreSQL's richer data types, extensible ecosystem, advanced replication and monitoring features, while exposing MySQL's limitations in data modeling, sequence support, tooling, and replication, and concludes that the best choice depends on specific workload requirements.
This comprehensive Redis guide covers its role as a core component in large‑scale architectures, explains common use cases, walks through installation and configuration options, details all primary data structures with commands and examples, and explores persistence, transactions, Lua scripting, replication, Sentinel, and cluster modes.
This article walks through the root causes of MySQL master‑slave replication delay, demonstrates step‑by‑step diagnostics using SHOW SLAVE STATUS, pt‑heartbeat, and binlog comparisons, and provides concrete configuration changes, query rewrites, hardware upgrades, and monitoring scripts that can shrink lag from dozens of seconds to sub‑millisecond levels.
This article explains how MySQL master‑slave replication works, covering its role in high‑availability and read/write separation, the responsibilities of the master and slave servers, the IO and SQL threads, common replication topologies, and the step‑by‑step data flow from binlog to relay log.
The article compares PostgreSQL and MySQL across data types, native sequences, extensions, monitoring tools, replication mechanisms, licensing, community governance, and MVCC implementation, showing why many Chinese tech giants favor PostgreSQL for complex, high‑consistency workloads while acknowledging MySQL’s strengths in simple web scenarios.
This article explains how MySQL binary logs can rapidly consume disk space, analyzes the root causes such as log format and workload, provides step‑by‑step diagnostics, and offers practical cleanup, configuration, replication, monitoring, and recovery strategies to prevent and resolve the issue.
This comprehensive guide explains MySQL binary log fundamentals, why they consume disk space, how to diagnose growth issues, and provides step‑by‑step cleanup, configuration, monitoring, and recovery strategies for both primary and replica servers.
The article analyzes why many Chinese cloud providers and enterprises prefer PostgreSQL to MySQL, detailing PostgreSQL's richer data types, native sequence support, extensible ecosystem, advanced monitoring, robust replication, open licensing, and MVCC implementation, while acknowledging MySQL's remaining advantages in specific scenarios.
This comprehensive guide explores MySQL 9.0's replication architecture, covering core principles, GTID and semi‑synchronous modes, various replication topologies, detailed troubleshooting steps, monitoring scripts, and best‑practice configurations, providing hands‑on examples and scripts to help engineers build and maintain robust, high‑availability database systems.
Amid China's push for independent, cloud‑native databases, leading firms like Tencent, Alibaba, Huawei and others have built PostgreSQL‑based solutions, and this article analyzes why PostgreSQL’s richer data types, true sequence objects, extensible ecosystem, advanced replication and licensing advantages make it a preferred choice over MySQL.
This article analyzes the severe replication‑delay issues in MySQL master‑slave setups, identifies four typical workload patterns that cause lag, demonstrates how AliSQL's AI assistant pinpoints the root causes, and explains the kernel‑level optimizations that completely remove the delay.
This article explains MySQL's redo log and binlog, why their write order can cause master‑slave inconsistencies, and how the two‑phase commit protocol atomically coordinates both logs to ensure reliable data consistency in distributed transactions.
This guide explains why MySQL replication lag spikes, how to distinguish IO‑thread pull problems from SQL‑thread apply bottlenecks, provides step‑by‑step commands, configuration examples, real‑world case studies, best‑practice recommendations, and monitoring setups to reliably troubleshoot and prevent replication delays.
This article explains Kafka's In‑Sync Replicas (ISR) mechanism, detailing its definitions, dynamic scaling, interaction with High Watermark, extreme unclean leader election scenarios, and practical tuning and troubleshooting tips for maintaining strong consistency and high availability in production clusters.
This comprehensive guide walks you through identifying the root causes of MySQL performance degradation in production, from gathering baseline metrics and analyzing slow‑query logs to examining execution plans, tuning parameters, applying configuration changes, and verifying improvements with concrete monitoring and backup strategies.
This comprehensive guide walks you through PostgreSQL 17 deployment, explains its multi‑process architecture and MVCC model, details environment requirements, shows essential configuration parameters, provides step‑by‑step backup and PITR procedures, demonstrates streaming replication setup, and shares best‑practice tuning, security, and monitoring tips for reliable production use.
If your MySQL 8.0 replica runs with super_read_only and the default innodb_undo_log_truncate=ON, a hidden undo‑log truncation bug can corrupt data, trigger a cascade of related bugs, and remain unresolved in 8.0 releases, demanding urgent checks and workarounds.
This guide presents practical, DBA‑tested MySQL replication best practices—including GTID, row‑based replication, mandatory primary keys, schema consistency, binlog tuning, read‑only protection, dedicated replication users, latency monitoring, parallel workers, and SSL encryption—to ensure reliable, predictable replica behavior.
The article analyzes why many leading Chinese tech firms adopt PostgreSQL despite MySQL’s popularity, detailing PostgreSQL’s richer data types, native sequence support, extensible ecosystem, advanced monitoring tools, robust replication, open‑source licensing, and MVCC implementation, while also acknowledging MySQL’s strengths in simple deployment and read‑heavy workloads.
The article examines why major Chinese cloud and technology providers are building distributed, cloud‑native or HTAP databases on PostgreSQL instead of MySQL, detailing differences in data types, sequences, extensions, monitoring, replication, licensing, and MVCC implementation.
This article explains MySQL master‑slave replication, covering its purpose, common topology patterns, the data flow from binlog to relay log, and a detailed step‑by‑step process for configuring asynchronous replication in production environments.
This comprehensive guide walks you through the reasons for MySQL master‑slave replication, deep technical concepts, step‑by‑step deployment, configuration tuning, monitoring, and real‑world troubleshooting to achieve a high‑availability database cluster that can survive production outages.
This article compares PostgreSQL and MySQL, highlighting PostgreSQL's richer data types, native sequences, extensible ecosystem, advanced monitoring, robust replication, open licensing, and MVCC implementation, while also acknowledging MySQL's strengths in simplicity and read‑heavy web workloads.
This article presents a step‑by‑step guide to designing and implementing a Kafka‑class distributed log‑based message queue kernel, covering architecture, sequential writes, sparse indexing, zero‑copy I/O, partitioning, replication, consumer‑group metadata, batch pipelines, crash recovery, and performance benchmarks.
This guide walks through Redis's evolution from single‑node replication to Sentinel and native Cluster, explaining each architecture's principles, configuration steps, advantages, drawbacks, performance trade‑offs, and practical deployment recommendations for building highly available and scalable caching systems.
The article compares PostgreSQL and MySQL, detailing PostgreSQL’s richer data types, true sequence support, extensible ecosystem, advanced monitoring and replication features, while also acknowledging MySQL’s simplicity and strong points, to help readers decide which database fits their workload best.
The article examines why major Chinese cloud providers and enterprises are building PostgreSQL‑based distributed, cloud‑native databases instead of MySQL, detailing PostgreSQL's richer data types, native sequence support, extensible ecosystem, advanced replication, licensing advantages, and MVCC implementation, while also noting MySQL's remaining strengths.
This article explains Kafka's high‑availability architecture, covering multi‑replica replication, leader‑follower election and failover, the role of In‑Sync Replicas, and producer acknowledgment settings with min.insync.replicas for reliable, zero‑data‑loss streaming.
The article compares PostgreSQL and MySQL, highlighting PostgreSQL's richer data types, true sequence support, powerful extensions, built‑in monitoring, advanced replication, open‑source licensing, and MVCC implementation, while acknowledging MySQL's strengths in quick deployment and read‑heavy workloads.
When MySQL replication falls behind, common culprits include oversized buffer pools, backup‑induced MDL waits, large transactions, slow queries, parallel replication quirks, and network issues, and this guide offers concrete configuration adjustments to restore sync and improve performance.
This article explains Kafka’s core mechanisms for preventing data loss, covering replica architecture, leader‑follower roles, ACK policies with ISR, log persistence and flush strategies, as well as producer idempotence and transactional support that together ensure reliable, exactly‑once delivery.
This guide explains how to boost Redis query per second (QPS) from 50,000 to 500,000 by applying horizontal sharding, read‑write separation with master‑slave replication, memory and data‑structure optimizations, and network‑level tuning, while providing concrete examples and configuration tips.
An in‑depth enterprise guide explains why backup and replication are critical for PostgreSQL, compares physical, logical, and logical replication methods, provides step‑by‑step command examples, outlines high‑availability architectures, automation scripts, disaster‑recovery procedures, monitoring queries, and common pitfalls to ensure robust data protection.
The article explains the main causes of duplicate Kafka messages—including producer retries, consumer offset handling, partition leader changes, and lack of idempotence—and provides practical configuration and design solutions to achieve exactly‑once delivery.
This comprehensive guide explains PostgreSQL's Write-Ahead Logging (WAL) fundamentals, its role in durability, crash recovery, PITR and streaming replication, details the checkpoint mechanism, essential monitoring queries, production‑grade configuration recommendations, backup and recovery procedures, and practical DBA checklists for reliable operations.
This article explains how Redis master‑slave replication provides hot backup, read‑write separation, high availability, and horizontal scaling by detailing its three‑stage workflow, full and partial synchronization mechanisms, key configuration options, and practical analogies for clear understanding.
Elasticsearch achieves billion‑scale search performance by combining horizontal sharding, immutable inverted‑index segments, a two‑stage distributed Query/FETCH model, and multiple replicas with a coordinator node to ensure high concurrency, scalability, and availability.
The article compares PostgreSQL and MySQL, highlighting PostgreSQL's richer data types, native sequence support, powerful extensions, superior monitoring and replication features, and open‑source licensing, while also noting MySQL's simplicity and ecosystem strengths, to explain why many Chinese enterprises choose PostgreSQL for their core databases.
The article compares PostgreSQL and MySQL across data types, sequence handling, extensions, monitoring tools, replication, licensing, and MVCC implementation, showing why many Chinese tech giants prefer PostgreSQL for complex, high‑availability workloads while acknowledging MySQL’s strengths in simple web scenarios.
An in‑depth guide to MySQL binary logs explains their role in replication, point‑in‑time recovery, auditing, and real‑time data pipelines, covering binlog formats, GTID, encryption, multi‑threaded replication, cleanup strategies, and practical mysqlbinlog commands for monitoring and troubleshooting.
This step‑by‑step guide shows how to design, install, configure, start, and verify a Redis Sentinel high‑availability setup with one master, two replica nodes, and three sentinel monitors, including client connection examples and common troubleshooting tips.
This article explains Redis master‑slave replication, covering its purpose for data redundancy, read/write separation, and high availability, and details the full‑synchronization and incremental‑synchronization processes with step‑by‑step diagrams.
This article examines why major Chinese technology companies are building distributed, cloud‑native and HTAP databases on PostgreSQL instead of MySQL, detailing PostgreSQL's richer data types, true sequence support, extensive extensions, superior monitoring tools, and robust replication mechanisms.
This article explains Redis master‑slave replication, detailing the full synchronization process that creates an RDB snapshot and streams buffered writes, as well as the incremental synchronization that resumes after a disconnection using PSYNC and the replication backlog.
The article dissects a high‑traffic flash‑sale interview question—how to guarantee zero order loss at 100,000 TPS when the master MySQL instance fails—by explaining the underlying performance‑consistency conflict, the three skills interviewers assess, and presenting five concrete, code‑driven solutions ranging from MySQL parameter tuning to semi‑sync replication, local message tables, group replication, and Redis‑Kafka traffic shaping.
This article explains MySQL master‑slave replication, why read/write splitting is essential, four practical read‑distribution strategies, the main causes of replication lag, four solutions for write‑after‑read consistency, multi‑slave allocation methods, replication modes, and a real‑world e‑commerce decision matrix, ending with a golden architecture recommendation.
This comprehensive guide walks you through troubleshooting PostgreSQL physical (stream) replication, covering environment prerequisites, anti‑pattern warnings, step‑by‑step diagnostics for replication lag, split‑brain scenarios, replication slot problems, monitoring setup with Prometheus, and best‑practice recommendations to keep your primary‑standby cluster healthy.
Learn how to set up Redis Sentinel for high‑availability caching, covering prerequisites, anti‑patterns, detailed configuration of master, replicas and Sentinel nodes, firewall rules, monitoring, failover testing, troubleshooting, performance tuning, backup, rollback and best practices—all achievable within a 30‑minute deployment.
This article explains MySQL master‑slave replication, covering asynchronous, semi‑synchronous, and full synchronous modes, their mechanisms, advantages, disadvantages, and ideal use cases for high availability, read/write separation, and strong consistency in large‑scale systems.
This comprehensive guide explains how to diagnose MySQL master‑slave replication lag, enable GTID mode, configure semi‑synchronous replication, optimize multi‑threaded replication, set up monitoring and alerting with Prometheus, and perform zero‑data‑loss failover using tools like Orchestrator and custom scripts.
This article explains why MySQL master‑slave replication can fall behind, outlines common causes of data inconsistency, and presents four comprehensive solutions—including architecture tweaks, multi‑threaded replication, configuration tuning, and Percona Toolkit verification—to achieve fast, stable, and accurate data synchronization.
This article explains how MySQL master‑slave replication works, covering the binlog mechanism, the three replication steps, and the three reliability modes—asynchronous, semi‑synchronous, and fully synchronous—while highlighting its impact on read throughput, backup, and disaster recovery.
This article explains MySQL master‑slave replication, covering its purpose for high availability, key features like real‑time disaster backup and read‑write separation, and the three essential steps—binlog recording on the master, I/O thread transfer to the relay log, and SQL thread replay on the slave.
Uber migrated its core database from PostgreSQL to MySQL because PostgreSQL suffered from index bloat, write amplification, high replication overhead, and limited MVCC support, prompting a detailed analysis of each issue, the improvements in newer PostgreSQL releases, and how MySQL’s architecture addresses these challenges.
This article outlines MySQL’s three primary replication architectures—async, semi‑sync, and full‑sync—detailing their mechanisms, typical topologies, performance trade‑offs, and suitable scenarios such as read‑heavy web services, high‑availability setups, and strict consistency requirements like financial transactions.
This guide explains how to configure Kafka producers with acks=all, enable idempotence, set appropriate retry and replication factors, and adjust broker flush intervals to achieve exactly‑once semantics and prevent message loss even during network glitches or broker failures.
This article explains MySQL replication architecture, detailing how binary logs are transferred, the roles of dump, I/O receiver, and SQL apply threads, the metadata tables they use, and key system variables for optimizing replication performance and durability.
This guide walks you through preparing the environment, choosing a data‑sync method, configuring both master and slave servers, verifying replication, troubleshooting common issues, and applying advanced settings to achieve a reliable, monitorable MySQL 5.7 master‑slave setup.
This article explains why version vectors are needed in multi‑leader and leaderless replication, describes their implementation and comparison rules, and presents practical conflict‑resolution strategies—including custom resolvers, last‑write‑wins, read‑repair, and request rejection—supported by Java pseudocode and diagrams.
This article explains Redis’s three clustering options—master‑slave replication, Sentinel high‑availability, and sharding—detailing their architectures, setup steps, synchronization mechanisms, advantages, drawbacks, and common interview questions, helping readers choose and implement the right solution for high‑performance, scalable data storage.
This tutorial walks through building a MySQL master‑slave cluster on Kubernetes using StatefulSets, covering local persistent volumes, storage classes, ConfigMaps, Secrets, Services for read‑write splitting, and step‑by‑step YAML manifests with verification commands to ensure proper replication and scaling.
This article provides a comprehensive overview of Redis, covering its core concepts, features, data types, caching patterns in Spring Boot, common cache pitfalls and solutions, performance reasons, eviction policies, persistence options, replication, and Sentinel high‑availability mechanisms.
This article explains the distinct yet collaborative roles of MySQL's Redo Log and Binlog, covering two‑phase commit, write‑ahead logging, flushing mechanisms, performance trade‑offs, and their use cases in crash recovery, replication, and point‑in‑time restoration.
Redis achieves million‑level concurrency by storing all data in memory, leveraging ultra‑fast read/write speeds, employing optimized data structures such as strings, hashes, lists, sets and sorted sets, using I/O multiplexing to handle many connections in a single thread, and scaling through master‑slave replication for high availability.
This guide walks through the reasons for MySQL master‑slave replication, explains its core mechanisms, details step‑by‑step environment planning, configuration, data initialization, replication setup, monitoring, failover with MHA, read‑write splitting using ProxySQL, performance tuning, troubleshooting, and best‑practice recommendations for enterprise‑grade high availability.
To prevent costly data loss during database failures, the XiaoHongShu team designed a resource‑efficient Binlog Server that doubles half‑sync replication speed to over 300 MB/s, enables automatic data recovery without manual intervention, and ensures RPO = 0 across fully deployed MySQL clusters.
This article explains the differences between MySQL’s default REPEATABLE READ (RR) and READ COMMITTED (RC) isolation levels, why large internet firms switch to RC, the mechanics of master‑slave replication, the three binlog formats, and how gap locks affect consistency and performance.
This article explains Redis master‑slave replication, covering its purpose for backup, read/write separation, and high availability, and details the seven‑step full‑copy process and the six‑step incremental sync process with illustrative diagrams.
This article explains the roles of StarRocks FE and BE nodes, details the metadata stored in FE, describes the leader‑follower‑observer architecture, and shows how BDB JE replication, journal logs, and checkpoint mechanisms ensure metadata synchronization and durability even after node failures.
This article explains how the REPLACE INTO statement can cause mismatched AUTO_INCREMENT values between MySQL master and replica after a failover, leading to primary‑key conflicts, and provides reproduction steps, underlying mechanics, and practical mitigation strategies.
This article examines write conflicts in single-leader replication, comparing exclusive and shared data, exploring uniqueness constraints, async replication delays, and various conflict‑resolution techniques such as unique indexes, bitmap mapping, LWW ordering, and multi‑version control for collaborative editing.
This article provides a comprehensive overview of MySQL master‑slave replication, explaining its core mechanisms, the push‑pull hybrid model, replication modes (asynchronous, full‑sync, semi‑sync), binlog formats, and practical strategies to reduce replication lag caused by large transactions, server load, and network constraints.
An experienced DBA recounts a midnight MySQL replication disaster where slave lag exceeded 60 seconds, then dissects the root causes—binlog formats, semi‑synchronous replication, and GTID—offering detailed configurations, performance tweaks, monitoring scripts, and best‑practice recommendations to prevent and resolve such failures.
This article explains the challenges of implementing causal consistency, compares it with linear and sequential consistency, describes how order guarantees are enforced in leader‑based replication, introduces Lamport timestamps and total‑order broadcast, and outlines practical approaches for achieving causal consistency in distributed systems.
Learn how to reduce MySQL 8 master‑slave replication delay from seconds to sub‑second levels by tuning five key parameters and applying three layers of parallel binlog replication, with detailed configuration examples, performance test results, troubleshooting tips, and ready‑to‑use scripts.
This article examines why multi‑leader and leaderless replication models struggle to provide linear consistency, explores write‑conflict handling, quorum‑based NWR mechanisms, sloppy quorum and hinted‑handoff techniques, and summarizes the trade‑offs involved in achieving strong consistency across distributed data centers.
This comprehensive guide walks you through a real production incident and then details MySQL configuration tuning, memory and thread settings, InnoDB core parameters, index design, query optimization cases, slow‑query analysis, read‑write splitting, monitoring scripts, sharding strategies, fault diagnosis, backup and recovery best practices, and high‑availability deployment, providing actionable tips and code examples for robust database performance.
This article examines eventual and linear consistency in leader‑based replication, explains read‑your‑writes and shared‑data scenarios, discusses replication lag, failover trade‑offs, multi‑data‑center risks, and shows how consensus systems like ZooKeeper and etcd implement true linear consistency.
This article breaks down MySQL's three core log types—undo log, redo log, and binlog—explaining how they support transaction atomicity, durability, MVCC, crash‑safe recovery, write‑ahead logging, and replication, while also covering buffer pool behavior and flush policies.
This article explains Redis' deployment models, core components, and the event‑driven engine that powers command processing, detailing the flow from client connection through the reactor loop, command parsing, execution, and response delivery with code examples and diagrams.
Learn step‑by‑step how to troubleshoot MySQL master‑slave replication problems, from verifying component roles and executing the correct SHOW SLAVE STATUS command inside the MySQL client, to fixing missing command errors, checking IO/SQL threads, and restarting replication in Docker‑based environments.
This article provides a comprehensive, step‑by‑step tutorial on deploying a MySQL master‑slave replication architecture using Docker containers, covering prerequisite checks, container setup, configuration files, replication user creation, master‑slave linking, testing data sync, and troubleshooting common issues.
This comprehensive MySQL tutorial covers everything from core concepts and architecture to practical CRUD operations, advanced queries, indexing, transaction control, stored procedures, triggers, replication, performance tuning, backup strategies, and real-world use cases, providing a complete roadmap for developers and DBAs.
The article combines practical advice for fresh graduates seeking internships and interview tips, shares a detailed ByteDance three‑round backend interview experience, explains MySQL master‑slave replication stages, binlog formats, and compares blocking, non‑blocking, multiplexed, and asynchronous I/O models.
This guide explains the principles of MySQL master‑slave replication, shows how to configure and verify replication, provides Dockerfiles and docker‑compose files for MySQL and Redis clusters, and demonstrates testing each cluster step by step.
This article compiles the ten most common MySQL error scenarios—from connection limits and replication conflicts to installation failures, password resets, truncate side‑effects, configuration pitfalls, charset issues, binlog formats, timeout problems, and file‑handle limits—offering clear diagnostic steps and concrete commands to resolve each case.
This tutorial walks through preparing the Linux environment, installing MySQL 5.7, configuring master and slave servers, creating replication users, verifying synchronization, troubleshooting common issues, and applying advanced options such as GTID and semi‑synchronous replication, all with complete command examples.
This tutorial walks you through checking the OS architecture, preparing the environment, downloading and extracting the MySQL 5.7 ARM package, configuring my.cnf, setting up auto‑start and environment variables, initializing the server, securing the root account, and configuring master‑slave replication on Linux.
Understanding high‑availability architectures involves mastering replication and fail‑over, balancing RTO and RPO, and choosing among four patterns—Active‑Standby, Active‑Active, Cold Standby, and Hot Standby—each with distinct synchronization, load‑balancing, and cost considerations for reliable system design.
This guide walks you through preparing multiple virtual machines, configuring MySQL server IDs, setting up both classic and GTID‑based master‑slave replication, and managing the replication with essential commands, complete with code examples and architecture diagrams.
This article analyzes a MySQL master‑slave replication failure where the SQL thread stopped with error 1594, detailing log inspection, CRC checks, relay‑log corruption, root‑cause identification, and step‑by‑step remediation procedures for restoring replication.
This article explains Redis's three clustering solutions—master‑slave replication, Sentinel mode, and sharding—detailing their architectures, setup steps, synchronization mechanisms, advantages, drawbacks, split‑brain handling, and common interview questions for developers.
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.
This article compiles the most frequently asked MySQL interview questions, covering fundamentals, storage engines, SQL optimization, indexing, transaction handling, replication, sharding, and performance troubleshooting to help readers master both theory and practical usage.
The article explains why the built‑in MySQL 5.7 Seconds_Behind_Master metric often misrepresents replication delay, analyzes its design flaws, and demonstrates how the Percona Toolkit's pt‑heartbeat tool can reliably measure master‑slave lag with real‑time precision.
This guide walks through setting up a MySQL master‑slave replication cluster on Kubernetes using a StatefulSet, local persistent volumes, delayed binding StorageClass, ConfigMap, Secret, and Services, then verifies replication and demonstrates horizontal scaling of slave nodes.
This article breaks down MySQL's three binlog formats—Statement, Row, and Mixed—detailing how each records changes, their advantages and drawbacks, and when to choose the most appropriate mode for reliable replication.
This article introduces the pt‑slave‑repair tool, explains the root causes of MySQL master‑slave replication errors 1032 and 1062, details its working principle, preparation steps, and provides concrete command‑line examples for automatically repairing these errors with minimal manual effort.
Redis 8.0-M03 adds an RDB channel replication feature that parallelizes RDB file transfer with write command streaming, reducing master node memory pressure and CPU load while improving full‑sync performance through a dedicated connection and configurable buffer limits.
