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.
Oracle’s 2026 AI database rollout fuses vector search, private AI agents, unified memory, and deep data security directly into the database engine, challenging the cloud‑centric data‑movement paradigm and prompting a market shift that could revive Oracle’s dominance while reshaping strategies for DBAs, AI engineers, and decision makers.
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 article explains MySQL master‑slave replication, covering its purpose for high availability and read‑write separation, typical one‑master‑multiple‑slaves architecture, the binlog‑based synchronization mechanism, and the roles of the master’s dump thread and the slave’s I/O and SQL threads.
The article debunks OpenAI's sensational claim of handling 800 million ChatGPT users with a single PostgreSQL instance, revealing a pragmatic hybrid architecture that combines many read replicas, Azure CosmosDB for write‑heavy workloads, and top‑tier hardware, while highlighting cost and complexity considerations.
This article explains why vector databases are essential for AI-driven unstructured data, surveys the current landscape of professional and extended vector databases, and provides a detailed technical comparison between Milvus and OceanBase, covering architecture, features, performance, and product positioning.
This article explains Tencent Cloud MongoDB’s backup and restore capabilities, the challenges posed by modern game workloads, and how the industry‑first key‑based flashback feature provides second‑level, fine‑grained, non‑disruptive data recovery, dramatically improving reliability and speed for game operators.
This article explains why NoSQL emerged to address the scalability and schema rigidity limits of relational databases, clarifies that MySQL data may reside in memory or on disk depending on the storage engine, and provides a practical guide to selecting the right database for various workloads.
This comprehensive guide walks you through MySQL InnoDB's core architecture, storage structures, indexing mechanisms, transaction and concurrency control, crash recovery, backup options, and practical performance‑tuning techniques, providing clear explanations and real‑world SQL examples.
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 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 article delves into the hierarchical logical architecture of MySQL’s InnoDB storage engine, detailing how table spaces, segments, extents, pages, and rows are organized, their functions, configuration options, and how they together enable efficient data storage, access, and transaction management.
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 article provides a comprehensive overview of MySQL's architecture, covering the client layer, connectors, lexical analysis, query optimizer, executor, storage engines, caching, and logging, and explains how each component contributes to a robust, high‑performance database system.
This article explains MySQL InnoDB's dual memory and on‑disk architecture, detailing the various tablespace types (system, file‑per‑table, general, undo, temporary), their internal structures (segments, extents, pages), configuration tips, and how tables, row formats, primary keys, auto‑increment lock modes, and B+Tree indexes are organized and managed.
This article explores the inner workings of InnoDB's architecture—including the Buffer Pool, Change Buffer, Adaptive Hash Index, and Log Buffer—detailing their designs, configuration parameters, performance impacts, and best‑practice recommendations for high‑throughput MySQL deployments.
BaikalDB, Baidu's distributed storage system, evolves from an OLTP‑focused engine to a hybrid HTAP architecture by introducing a vectorized query engine and a massively parallel processing (MPP) layer, addressing compute and resource bottlenecks for large‑scale analytical workloads while preserving transactional guarantees.
This article objectively compares middleware‑based sharding with NewSQL distributed databases, examining architecture, distributed transactions, performance, high availability, scaling, SQL support, storage engines, and ecosystem maturity to help architects decide which solution fits their specific workload and operational constraints.
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.
The article explains how MySQL Shell and MySQL Router 9.2 introduce Routing Guidelines, a declarative, context‑aware query routing feature that lets administrators define fine‑grained rules based on server roles, session attributes, and network information to improve latency, load‑balancing, and fault‑tolerance in complex MySQL topologies.
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 objectively compares NewSQL databases with middleware‑based sharding, dissecting their core architectures, distributed transaction handling, high‑availability designs, scaling mechanisms, SQL support, storage engines, and maturity to help engineers decide the most suitable solution for their workloads.
This article examines DeepSeek, a Chinese AGI‑focused AI model, and demonstrates how prompt engineering can enable it to assist database architects, development DBAs, and operations DBAs across various real‑world scenarios, while also discussing its broader impact on individuals, vendors, and enterprises.
This article explains MySQL’s logical architecture, details the storage‑engine API and its key components such as connectors, parsers, optimizer, caches, and file system interaction, and provides step‑by‑step guidance on creating, opening, locking, scanning tables and building a custom storage engine.
This article explains MySQL’s internal architecture, covering how data pages, B+‑tree and hash indexes, the Buffer Pool, Adaptive Hash Index, Change Buffer, Undo/Redo logs, the InnoDB storage engine, and the server layer work together to provide fast, reliable CRUD operations and support replication.
This article provides a comprehensive analysis of MySQL’s internal architecture, detailing the four-layer design, the server service layer’s parsing, optimization and execution components, and the critical roles of Undo Log, Redo Log, and Binlog in ensuring ACID transaction properties.
This article provides a comprehensive overview of MySQL's layered architecture, the functions and core components of the server layer, and detailed explanations of Undo Log, Redo Log, and Binlog mechanisms that together ensure the ACID properties of transactions, including practical execution flows for queries and updates.
The article explains how thousands of simultaneous client connections to a single PostgreSQL primary can cause severe write‑performance degradation, how introducing a connection pool such as pgBouncer reduces active backend processes dramatically, and why external pooling is preferred over built‑in solutions, illustrated with real‑world examples and a reference to the open‑source Pigsty distribution.
Redis primarily operates with a single thread using I/O multiplexing (select, poll, epoll) to handle massive concurrent connections, while newer versions introduce optional multi‑threaded networking and use child processes for persistence, maintaining its core single‑threaded design for data processing.
This article examines the QiaoFang SaaS platform’s multi‑tenant database architecture, tenant data governance, multi‑partition service design, and operational practices such as database operations, cleanup, and monitoring, highlighting the challenges and solutions for large‑scale real‑estate brokerage services.
TDE‑ClickHouse, the core engine of Baidu MEG’s Turing 3.0 ecosystem, delivers sub‑second, self‑service analytics on petabyte‑scale data by decoupling compute, adding multi‑level aggregation, high‑cardinality and rule‑based optimizations, a two‑phase bulk‑load pipeline, cloud‑native deployment, and a lightweight meta service, now powering over 350 000 cores, 10 PB storage and more than 150 000 daily BI queries with average response times under three seconds.
This article explains MySQL's logical architecture, detailing the four main layers—connection, core service, storage engine, and data storage—while providing code examples and insights into each component's role in the widely used open‑source relational database.
This article investigates the theoretical maximum number of records a MySQL SELECT can return by examining max_allowed_packet, row‑size limits, column count, page‑size constraints, row‑overflow mechanisms, and practical experiments that reveal how these factors together bound query results.
The article outlines MySQL’s layered architecture—connector, parser, optimizer, executor, and binary log in the server layer and pluggable storage engines like InnoDB—then walks through the step‑by‑step processing of SELECT and UPDATE statements, highlighting permission checks, caching, plan selection, redo and binlog handling for crash‑safe durability.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding, examining their architectural advantages, distributed transaction handling, high‑availability mechanisms, scaling and sharding strategies, storage engine differences, ecosystem maturity, and provides guidance on selecting the appropriate solution for various workloads.
This article recounts how SQLite was created by Richard Hipp to solve reliability issues on a U.S. Navy destroyer, evolved from a simple file‑based engine into an open‑source, B‑Tree powered embedded database that now powers billions of devices, smartphones, browsers, and applications worldwide.
This article examines the 70‑year evolution of databases, explains how large‑model AI drives the rise of vector databases and Retrieval‑Augmented Generation (RAG), outlines the four‑stage RAG workflow, compares Baidu’s self‑built VectorDB with open‑source alternatives, and showcases real‑world deployments that highlight performance, scalability, and enterprise benefits.
This article reviews the 70‑year evolution of databases, explains how vector databases and Retrieval‑Augmented Generation (RAG) are reshaping AI applications, and details Baidu Intelligent Cloud's VectorDB architecture, performance advantages, real‑world use cases, and future trends in data engineering.
This article introduces X‑Stor, a cloud‑native NoSQL service that supports multiple data models and process‑level multi‑tenant isolation, explains its architecture and design choices, and presents extensive experimental results that compare its performance and resource management against single‑model databases.
This article outlines the progressive evolution of database architectures—from simple monolithic designs to cold‑hot separation, read‑write splitting, and horizontal sharding—explaining each pattern, its components, and the performance and scalability benefits they bring to large‑scale systems.
Despite the hype around NoSQL, this article argues that SQL and relational databases remain the superior choice for transactional data, tracing two decades of research, highlighting the limitations of NoSQL, and showing how modern databases now incorporate the best features of both worlds.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding solutions, examining their architectures, transaction models, scalability, high‑availability mechanisms, storage engines, maturity, and offering a decision framework to help engineers choose the most suitable approach for their workloads.
Redis, an open-source in-memory NoSQL database, is explored in depth covering its high-performance features, typical use cases, evolution, architecture, data types and commands, followed by an overview of Tencent Cloud Redis services and a brief advertisement for a DevOps certification program.
This article provides a comprehensive overview of Apache Doris, explaining its frontend and backend nodes, storage structures such as tablets, rowsets, and segments, replication mechanisms, partitioning versus bucketing, indexing types, compaction processes, and high‑availability strategies through a detailed Q&A format.
This article explains how Redis achieves tens of thousands of QPS on average hardware, breaks down the technical reasons behind its speed—including C implementation, in‑memory design, epoll‑based I/O multiplexing, and a single‑threaded event loop—while also detailing the evolution to multithreaded I/O in later versions.
This article details Uber's Docstore distributed database challenges and explains the design, architecture, and implementation of CacheFront—a transparent, high‑performance caching layer that reduces latency, improves scalability, and maintains strong consistency across microservices.
This article provides a comprehensive overview of Hybrid Transactional/Analytical Processing (HTAP) databases, detailing the four architectural patterns, five core technologies, and a comparative analysis of major Chinese HTAP products such as TiDB, OceanBase, PolarDB‑X, TDSQL, GaussDB and GreatSQL, while also discussing their characteristics and remaining challenges.
This article explains how Vitess was created to overcome MySQL leader‑follower replication limits at YouTube, detailing its sidecar VTTablet, stateless VTGate router, topology key‑value store, and scaling strategies that enable billions of users to be served reliably.
This article explains why MySQL master‑slave replication can become delayed—including single‑threaded binlog processing, high load, network latency, and configuration issues—and provides detailed troubleshooting steps and practical solutions such as semi‑synchronous replication, hardware upgrades, and configuration tuning.
This article walks through how MySQL processes a SELECT query, detailing the server and storage engine layers, the roles of the connector, query cache, parser, optimizer, and executor, and provides practical command‑line examples to illustrate each step.
This article analyzes the PolarDB Serverless paper awarded at ICDE 2024, detailing its shared‑storage architecture, seamless cross‑machine migration, strong‑consistent read scaling, implementation techniques, experimental performance versus Aurora Serverless, and its rapid commercial adoption.
This article objectively compares NewSQL distributed databases with traditional middleware‑based sharding solutions, examining their architectures, distributed transaction support, high availability, scaling, storage engines, SQL capabilities, maturity, and suitability for various workloads, to help architects decide which approach best fits their needs.
This article objectively compares NewSQL databases and middleware‑plus‑sharding architectures, examining their core principles, distributed transaction handling, high‑availability mechanisms, scaling and sharding strategies, SQL support, storage engines, and maturity to help engineers decide which solution fits their workload.
This article explains MySQL’s logical architecture, details the pluggable storage‑engine API, lists the default engines, and provides step‑by‑step guidance with code examples on how to create a custom MySQL storage engine.
This article objectively compares middleware‑based sharding with modern NewSQL distributed databases, examining their architectural differences, performance, transaction support, scalability, high‑availability, and operational considerations, to help practitioners decide which approach best fits their workload and organizational constraints.
This article explains GaussDB's system architecture, the roles of GTM, CN, and DN, the SQL and storage engines, parsing stages, rule‑based and cost‑based optimizers (including AI‑based techniques), distributed query plans, execution operators, and the parallel execution framework that together enable high‑performance SQL processing in a cloud‑native distributed database.
This article presents a comprehensive overview of TuGraph-DB, covering the historical development of graph query languages, the capabilities and future plans of the TuGraph 4.0 query engine, and the proposed architectural evolution to support multiple languages and storage back‑ends.
This article examines Alibaba's internal Doris KV storage system, detailing why large companies build proprietary data products, the project's kickoff criteria, the two‑layer architecture, virtual‑node routing, failover mechanisms, and cluster scaling strategies for massive KV workloads.
BTS (Baidu Table Storage) is Baidu Intelligent Cloud’s high‑performance, low‑cost semi‑structured NoSQL service that evolved from single‑table to multi‑model (wide tables, time‑series, soon documents), featuring a three‑layer compute‑storage separation architecture, multi‑level caching, hot‑backup HA, and supporting massive IoT, AI, autonomous‑driving and monitoring workloads.
This article explains the complete lifecycle of a MySQL SELECT statement, covering the server and storage‑engine layers, the roles of the connector, query cache, parser, optimizer and executor, and provides concrete command‑line and SQL examples.
This article traces SQLite’s origins from a 2000 Navy project, explains how its first version wrapped GDBM, details its layered architecture and code flow, and shows how Richard Hipp’s philosophy of building every component himself turned SQLite into the ubiquitous embedded database we see everywhere today.
This article examines the current landscape of Chinese databases, compares centralized and distributed architectures, outlines when distributed solutions are truly needed, provides performance test data, and offers practical advice on sharding, SQL design, and avoiding cross‑node bottlenecks.
This article examines the trade‑offs between centralized and distributed OLTP databases, presents industry usage statistics, performance benchmarks, practical questions for migration, and detailed guidance on sharding, SQL design, and operational considerations to help decide when a distributed solution is truly needed.
The article explains how Corona leverages three time‑series databases—InfluxDB for storing pre‑aggregated user metrics and platform health data, ClickHouse for real‑time multidimensional log analysis with aggregations, and ElasticSearch for full‑text searchable log monitoring—detailing their schema designs and query examples.
This article provides a comprehensive overview of TiDB, an open‑source distributed NewSQL database, covering its origins, architecture components, high‑availability design, HTAP capabilities, MySQL compatibility, differences from traditional SQL and NoSQL, and practical deployment scenarios.
This article explains the reasons for read/write splitting, compares direct‑client and proxy‑based master‑slave setups, and presents five practical strategies—including forcing reads to the master, sleep delays, lag checks, master‑position waiting, and GTID waiting—to mitigate stale reads caused by MySQL replication lag.
The article explains why master‑master MySQL architectures are discouraged, outlines the pitfalls of dual‑write setups, and provides step‑by‑step instructions using dbops to deploy a master‑slave topology and manually create a reversible master‑master configuration for testing.
This article explains the evolution from traditional SQL and NoSQL to NewSQL, outlines the limitations of each, and provides an in‑depth look at TiDB—a cloud‑native, distributed NewSQL database—covering its architecture, core features, high‑availability design, compatibility with MySQL, and typical use cases.
This article presents an in‑depth overview of MatrixOne, an open‑source hyper‑converged cloud‑native database, detailing its three‑tier architecture of compute, data and file services, and explains the design and implementation of its OLAP engine, including parser, planner, optimizer, and push‑based execution pipeline.
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.
The article examines PostgreSQL's traditional process‑oriented architecture, compares it with a proposed thread‑based model, outlines the advantages and disadvantages of each, and discusses community perspectives on transitioning to threads for improved performance and resource efficiency.
This article explains MySQL's four‑layer logical architecture, describes high‑performance read strategies, details data pages, buffer pool and LRU algorithm, and provides comprehensive guidance on index structures, optimization techniques, and best practices for improving query performance.
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 article reviews the origins, core characteristics, traditional and logical architectures of data warehouses, explores emerging trends such as massive real‑time data, and outlines Huawei Cloud GaussDB(DWS) evolution toward a cloud‑native, elastic, lake‑warehouse integrated solution.
This article introduces Abase, ByteDance’s massive online KV storage system, detailing its evolution from a single‑cluster KV service to a multi‑region, multi‑tenant platform, and explains the high‑availability challenges and the leaderless multi‑write architecture, hybrid logical clocks, quorum settings, and performance optimizations that enable hundred‑billion QPS and sub‑10 ms latency.
This article reviews recent Chinese database market reports, outlines the evolution of database management systems, describes architectural layers, HTAP solutions, compression techniques, storage index structures, intelligent governance, and deployment models, highlighting both technical trends and future directions.
This article provides a detailed comparison of two document‑oriented NoSQL databases, MongoDB and CouchDB, covering their architectures, features, replication models, mobile support, query mechanisms, code examples, and guidance on choosing the appropriate system based on application requirements.
The article explains how single‑instance MySQL struggles with huge tables, resource‑starved databases, and high read traffic, and argues that sharding middleware is being replaced by modern distributed databases such as TiDB, OceanBase, Aurora, and PolarDB as the sustainable scaling solution.
This article explores MySQL’s write‑ahead log, two‑phase commit, engine plugins, memory management, lock strategies, and state‑machine design, showing how these internal mechanisms can inspire more reliable, scalable, and maintainable business system architectures.
The author stress‑tested Milvus 2.1.4’s cloud‑native, micro‑service architecture—detailing its write and search paths, evaluating FLAT index performance across 100 K to 10 M 512‑dim vectors, uncovering scaling, scheduler, segment‑rebalance, and upgrade issues, and concluding the system is robust but benefits from graph‑based indexes and Helm‑driven scaling.
This article explains MySQL’s three‑tier logical architecture—from client services to core query processing and storage engines—and details the four ANSI SQL transaction isolation levels, highlighting their behavior, advantages, and trade‑offs in MySQL.
The article explains MySQL's continued dominance in the database market, presents recent developer survey statistics, describes its three‑layer logical architecture, and introduces the new edition of the "High Performance MySQL" book as a guide for modern database professionals.
This article demystifies MySQL’s processing pipeline by tracing a simple UPDATE statement through the application, service, and storage engine layers, detailing connection handling, SQL parsing, optimization, execution, buffer pool management, and the roles of undo and redo logs in ensuring data integrity.
This article summarizes recent Chinese database product strategy reports, outlining database definitions, management systems, design processes, product classifications, architectural layers, HTAP technology, compression methods, storage index structures, intelligent autonomous optimization, and deployment models, highlighting trends and future directions in the database industry.
This article explains how Redis evolved from a single‑threaded event‑loop architecture using I/O multiplexing and the Reactor pattern to a multi‑threaded I/O model and an enhanced BIO system with lazyfree, detailing design decisions, source‑code excerpts, performance impacts, and practical lessons for developers.
This article examines Redis 6.0 and 5.0 new features, compares various deployment architectures—including master‑replica, cluster, and read/write‑split—and provides practical guidance, code examples, and performance considerations to help engineers select the optimal Redis setup for production environments.
This guide explores five essential dimensions of MySQL performance tuning—including connection configuration, architectural choices such as caching and read‑write splitting, optimizer settings, storage engine selection, and schema design—providing concrete commands, formulas, and best‑practice recommendations to accelerate query execution and reduce load.
The article compares MySQL's limited join capabilities with PostgreSQL's richer options, explains why multi‑table joins can be slower than separate single‑table queries performed in the service layer, and outlines how decomposing joins improves caching, scalability, and overall system performance.
This article examines why single-node databases no longer meet modern internet workloads, explores MySQL replication models (master‑slave, asynchronous, semi‑synchronous, group replication), discusses high‑availability solutions such as MHA, MGR and Orchestrator, and outlines vertical and horizontal sharding techniques along with their trade‑offs.
The article introduces Alibaba Cloud's Graph Database (GDB), detailing its product features, supported query languages, high‑performance and high‑availability architecture, parallel execution engine based on the Volcano model and Morsel‑driven parallelism, and showcases real‑world use cases such as DingTalk friend recommendation and Hema Fresh recommendation.
This article explains ClickHouse’s MPP columnar design, complete DBMS capabilities, columnar storage, vectorized execution, multi‑master architecture, real‑time queries, sharding, and performance‑focused hardware and algorithm choices that together deliver its superior speed.
The article presents a comprehensive guide to distributed storage, organizing its design and implementation into seven essential dimensions—replication, storage engine, transaction processing, analytical query execution, multi‑core scaling, compute engine architecture, and compilation techniques—each explained with core concepts, challenges, and practical considerations.
This article presents a comprehensive overview of how TiDB's HTAP capabilities enable real‑time multi‑source data processing for financial intelligent risk control, detailing the overall risk‑control architecture, digital transformation challenges, TiDB‑based solutions, practical implementations, and future outlooks.
This article presents a comprehensive technical overview of MatrixOne's HTAP journey, detailing the challenges of hybrid transaction/analytical processing, classifying existing HTAP approaches, describing MatrixOne's storage architecture, AOE and TAE engines, and outlining future roadmap and performance considerations.
This article explains MySQL's layered design, detailing how the Server and InnoDB storage engine interact, the role of the Buffer Pool in caching data, and the functions of redo log, undo log, and binlog in ensuring durability, recovery, and replication.
The 2022 Gdevops Global Agile Operations Summit in Guangzhou featured a technical session by Zheng Zengquan of Aikesheng on MySQL high‑availability architecture, covering data consistency, production‑ready solutions, and a comparison of MGR versus traditional master‑slave setups, with the full PPT available for download.
Learn why HBase outperforms MySQL for massive, historical data, explore key rowkey design principles such as composite keys, field ordering, length alignment, and hotspot mitigation, and see practical examples like cold‑hot data separation and transaction logs, plus a concise overview of HBase’s core architecture.
This article walks through the complete lifecycle of a MySQL SELECT statement, from establishing the TCP connection and authentication, through query cache, parsing, optimization, and execution, detailing how the server and storage engine collaborate and explaining concepts like index usage, connection handling, and memory management.
This article explains MySQL’s core architecture, detailing components such as connection pools, SQL interface, optimizer, and storage engine plugins, then compares MyISAM and InnoDB, and dives deep into InnoDB’s memory structures, buffer pool, adaptive hash index, tablespaces, and redo log mechanisms.
This article provides a comprehensive overview of Doris's architecture—including its FE and BE components, metadata management, data organization, execution planning—and details its major features such as adaptive join aggregation, vectorized execution, materialized views, and Elasticsearch integration, supplemented with example DDL and query code.
