Tagged articles
database consistency
39 articles · Page 1 of 1

ITPUBAug 27, 2026 · Industry Insights
The article recounts a speaker’s twelve‑year journey through DTCC conferences, linking database consistency to philosophical ideas, outlining the C² framework, and tracing China’s shift from Oracle‑centric DBA practices to open‑source and domestic databases while previewing his upcoming books.
C2 frameworkChinese database industryDTCC
0 likes · 22 min read

The article explains the delayed double‑delete cache‑invalidation pattern, its four major drawbacks in high‑concurrency environments, and presents four production‑grade alternatives—event‑driven binlog updates, distributed‑lock with versioning, write‑through proxy layers, and logical‑delete with async cleanup—used by leading Chinese internet firms to achieve reliable data consistency.
CachingDistributed LockVersioning
0 likes · 21 min read

This article explains why MySQL master‑slave replication lag causes dirty reads, breaks down the asynchronous replication pipeline, and presents three practical mitigation strategies—including semi‑synchronous replication, forcing reads from the master, and cache double‑delete techniques—so you can choose the right solution for your workload.
MySQLReplication LagSemi‑synchronous
0 likes · 9 min read

This article explains how XiaoHongShu’s database team built a lightweight Binlog Server to accelerate semi‑synchronous MySQL replication beyond 300 MB/s, achieve RPO=0 data‑loss‑free failover, and improve high‑availability without manual intervention, backed by performance tests and detailed architecture diagrams.
Binlog ServerMySQLRPO=0
0 likes · 15 min read

MySQL employs a two‑phase commit to synchronize InnoDB’s redo log with the server’s binlog, ensuring atomicity during transaction commits and preventing data inconsistencies during crash recovery or replication, while also introducing lock contention, extra I/O, and potential blocking.
Two-Phase Commitbinlogdatabase consistency
0 likes · 5 min read

The article walks through the DIKW model, illustrates how a homestay platform’s data stack evolves from a simple MVP to a complex, AI‑enabled distributed system, and details the design of a unified Data Warebase that combines database and data‑warehouse capabilities to meet performance, correctness, and real‑time demands, backed by concrete case studies and measurable improvements.
AI integrationbig datadata warehouse
0 likes · 31 min read

This article examines the data consistency challenges of writing to both databases and caches, outlines four common double‑write strategies, analyzes their pitfalls—especially under high concurrency—and recommends the optimal approach of writing to the database then deleting the cache, while discussing retry mechanisms, scheduled tasks, message queues, and binlog listeners.
Cachedatabase consistencyhigh concurrency
0 likes · 15 min read

This article explains MySQL's doublewrite buffer mechanism, how it ensures data consistency by writing to a redo log before disk, provides configuration steps to enable it, and outlines performance optimization techniques such as adjusting redo log size, separating log files, and tuning flush settings.
Doublewrite BufferInnoDBMySQL
0 likes · 4 min read

This article examines the challenges of data consistency verification during database migrations, reviews existing tools like pt-table-checksum, sync‑diff‑inspector and gt‑checksum, outlines essential capabilities, and proposes a detailed workflow and future enhancements for a versatile, low‑impact consistency checking solution.
MySQLchecksum toolsdata migration
0 likes · 11 min read

The article examines how to maintain data consistency between caches and databases during dual-write operations, categorizes data into three levels, evaluates four update strategies, and proposes solutions such as delayed double deletion, message‑queue compensation, and binlog‑driven cache synchronization.
MySQLdatabase consistency
0 likes · 8 min read

The article analyzes three data‑level classifications, examines four cache‑database write strategies, discusses their pros and cons, and presents practical solutions such as delayed double deletion, message‑queue compensation, and binlog‑driven cache updates to maintain consistency.
Message Queuecache invalidationdatabase consistency
0 likes · 8 min read

This article explains why cache‑database consistency is a classic challenge, compares common update‑then‑delete patterns, analyzes concurrency and master‑slave delay issues, and recommends reliable solutions such as asynchronous retries with message queues or binlog subscription to achieve eventual consistency.
Cachingasynchronous-retrydatabase consistency
0 likes · 18 min read

This article explains the principles of MySQL semi‑synchronous replication, analyzes how data consistency is maintained during high‑availability failover, presents detailed step‑by‑step transaction flow, discusses scenarios causing GTID divergence, and offers testing methods and remediation techniques for DBA practitioners.
DBAGTIDMySQL
0 likes · 14 min read

Redis 7.0 introduces a suite of groundbreaking features—including the Function command family, Multi‑part AOF, sharded Pub/Sub, and client‑eviction controls—while also expanding use‑case scenarios, improving consistency, and highlighting the growing contributions of the Chinese developer community.
7.0Client EvictionFunction
0 likes · 17 min read

The article explains how micro‑service architectures create data‑consistency challenges that require distributed transaction strategies, compares strong‑consistency protocols like 2PC/3PC with eventual‑consistency approaches such as TCC and Saga patterns, and discusses their trade‑offs, implementation complexity, and suitability for real‑world scenarios like a points‑based sign‑in system.
SagaTCCdatabase consistency
0 likes · 11 min read

This article explains the fundamentals of distributed transactions, the ACID properties, various consistency models (strong, weak, eventual), sharding strategies (vertical and horizontal), the CAP and BASE theories, and the practical implementations of two‑phase, three‑phase, and TCC commit protocols, highlighting their advantages and drawbacks.
2PC3PCBASE
0 likes · 22 min read

The article examines tiered data storage and evaluates four cache‑synchronization strategies—updating the database before the cache, deleting the cache before updating the database, updating the cache before the database, and deleting the cache after a database update—highlighting their trade‑offs and practical solutions such as delayed double deletion, message‑queue retries, and binlog‑driven cache updates.
BackendCachingMySQL
0 likes · 8 min read

The article analyzes the challenges of maintaining data consistency when using both cache (local memory or Redis) and a database, classifies data by real‑time requirements, evaluates four double‑write strategies, and proposes practical solutions such as delayed double deletion, message‑queue compensation, and binlog‑driven cache updates.
BackendCachedata synchronization
0 likes · 8 min read

This article explains how InnoDB’s two‑phase commit mechanism keeps the redo log and binlog logically consistent, illustrating failure scenarios, the impact on data recovery, and how the prepare‑commit split prevents inconsistencies in MySQL’s storage engine.
InnoDBMySQLTwo-Phase Commit
0 likes · 4 min read

This article explains the concept of anti‑entropy as a key mechanism for achieving eventual consistency in distributed database systems, illustrates how XDB Enterprise handles node failures and data drift, and shows practical examples of repairing inconsistencies using the AE service.
Anti-entropyXDB Enterprisedata replication
0 likes · 10 min read

This article explains why caching improves performance, examines the trade‑offs between cache utilization and data consistency, analyzes concurrency‑induced inconsistency scenarios, compares update‑then‑delete versus delete‑then‑update approaches, and recommends asynchronous retry with message queues or binlog subscription to reliably keep cache and database in sync.
CacheDelayed Double DeleteMaster-Slave Replication
0 likes · 19 min read

This article explains rigid (strong consistency) distributed transactions, detailing the XA protocol and the classic two‑phase commit (2PC) and three‑phase commit (3PC) mechanisms, their workflows, advantages, limitations, and practical considerations for database systems.
Two-Phase CommitXA protocoldatabase consistency
0 likes · 15 min read

This article explains why cache‑database consistency is a classic problem, analyzes various update‑order and deletion strategies, discusses concurrency and replication delays, and recommends using the "update database then delete cache" approach combined with asynchronous retries via message queues or binlog subscription to achieve reliable eventual consistency.
database consistency
0 likes · 23 min read

The article uses a personal bank‑transfer incident to introduce local transaction concepts, explains the CAP theorem, examines the challenges of distributed transactions, and presents a message‑queue‑based design with transaction logs and compensation mechanisms to ensure consistency and idempotency.
CAP theoremMessage QueueTransactions
0 likes · 15 min read

This article explains how to guarantee data consistency when updating multiple tables or services by using local transactions for single‑node systems, two‑phase commit for distributed databases, and reliable message‑queue patterns—including RocketMQ transactional messages—to achieve eventual consistency and handle duplicate delivery.
Message QueueRocketMQTransactional Messaging
0 likes · 21 min read

This article analyzes how MySQL slave crashes can cause inconsistencies between master info and relay log positions during sync_master_info and sync_relay_log_info processes, presents case studies of duplicated events, explains the impact of different storage repositories (FILE vs TABLE), and recommends configuration settings to achieve server‑crash‑safe replication.
MySQLRelay LogReplication
0 likes · 15 min read

This article provides a comprehensive technical guide to distributed transactions, covering ACID fundamentals, consistency models, sharding techniques, CAP and BASE theories, and detailed implementations of two‑phase, three‑phase, and TCC protocols, while highlighting their advantages, limitations, and practical considerations.
BASE theoryCAP theoremSharding
0 likes · 23 min read


21CTOAug 5, 2020 · Databases
Distributed transactions require careful coordination to maintain consistency across multiple nodes, and this article explores core concepts such as atomic operations, two‑phase and three‑phase commit protocols, deterministic Calvin ordering, Google Spanner’s TrueTime and Paxos‑based approach, as well as advanced techniques like Percolator, RAMP, and coordination avoidance.
Calvin protocolRampSpanner
0 likes · 33 min read

This article explains the fundamentals of distributed transactions, compares five major solutions—including XA two‑phase commit, TCC, Saga, message‑based approaches, and maximum‑effort notification—covers their architectures, advantages, drawbacks, and provides guidance on selecting the right model for micro‑service systems.
SagaSeataTCC
0 likes · 27 min read

This article explains typical cache issues such as cache avalanche, cache penetration, concurrent write conflicts, and database‑cache write inconsistency, and provides practical mitigation strategies including high‑availability setups, circuit breakers, placeholder values, distributed locks, double‑delete, and cache‑aside patterns.
Cache AsideDistributed Lockcache avalanche
0 likes · 8 min read

This article explains the ACID principles of relational databases versus the CAP principles of NoSQL systems, illustrates why distributed systems can only satisfy two of consistency, availability, and partition tolerance, and discusses how Eureka and Zookeeper embody AP and CP choices, especially during high‑traffic events like Double‑11.
CAP theoremEurekaNoSQL
0 likes · 3 min read

This article explains the fundamentals of distributed transactions, why they arise in modern micro‑service architectures, outlines the ACID properties, presents typical use cases such as payments and order processing, and compares common implementation approaches like 2PC, message‑based eventual consistency, and TCC.
2PCMessage QueueTCC
0 likes · 12 min read


ITPUBMay 24, 2018 · Databases
This article reviews Ant Financial's evolution of distributed transaction solutions—from early SOA consistency issues to the high‑performance TCC model, the developer‑friendly FMT approach, and the real‑time XA integration with OceanBase—highlighting architectural decisions, optimizations, and practical outcomes.
TCCXAdatabase consistency
0 likes · 20 min read

This article details Ele.me's design and implementation of a MySQL bidirectional replication component (DRC) that enables sub‑second, high‑throughput data synchronization across Beijing and Shanghai data centers, addressing latency, consistency, and failover challenges in a multi‑active environment.
High AvailabilityMulti-ActiveMySQL
0 likes · 18 min read

This article explains transaction isolation levels, dirty reads, and phantom reads, compares how major databases such as SQL Server, PostgreSQL, MySQL, Oracle, DB2, MongoDB, CouchDB, Couchbase, and Cassandra implement these concepts, and highlights the performance‑security trade‑offs of each isolation level.
Dirty ReadNoSQLSQL
0 likes · 16 min read

MySQL 5.7.17 introduced Group Replication, a feature that ensures full data consistency across multiple MySQL nodes by synchronizing changes, offering high consistency, fault tolerance, elasticity, and flexible single‑master or multi‑master modes, making it suitable for elastic replication, high‑availability sharding, and as a replacement for traditional master‑slave replication.
Group ReplicationMySQLdatabase consistency
0 likes · 4 min read

The article explains the drawbacks of traditional two‑phase commit distributed transactions—reduced availability, performance, and scalability—and proposes a message‑queue‑plus‑state‑table pattern with idempotent processing to achieve eventual consistency while improving system throughput.
Message QueueTwo-Phase Commitbackend architecture
0 likes · 7 min read

Learn how to diagnose MySQL master‑slave data drift using Percona Toolkit’s pt‑table‑checksum, configure necessary replication parameters, and automatically reconcile differences with pt‑table‑sync, including installation steps, command syntax, required privileges, and troubleshooting common errors for reliable database consistency.
MySQLReplicationdatabase consistency
0 likes · 13 min read

This article explains why cache and database can become inconsistent in distributed systems, why the "invalidate‑cache‑then‑write‑DB" rule is preferred, and presents practical serialization techniques—modifying DB and service connection pools—to guarantee per‑key sequential execution while maintaining availability and load balance.
CacheSerializationbackend architecture
0 likes · 11 min read
