This article explains the fundamentals of database transactions, the ACID properties, implementation details such as transaction logs and concurrency control, and explores distributed transaction solutions including two‑phase and three‑phase commit, XA, Saga patterns, and message‑based approaches.
This article explains the fundamentals of database transactions, the ACID properties, the challenges of distributed transactions, and compares various solutions such as 2PC, TCC, local message tables, MQ transactions, and Saga, helping readers choose appropriate approaches based on consistency and availability requirements.
The article explains the CAP theorem, its three properties—consistency, availability, and partition tolerance—how they influence database design, compares CA, CP, and AP classifications with examples, and discusses related concepts such as ACID, BASE, and practical design choices for distributed systems.
This article explains InnoDB's transaction and index principles, covering ACID properties, transaction logs, MVCC, locking mechanisms, and B+ tree index structures to help backend developers understand how InnoDB ensures data consistency and high concurrency.
MongoDB 4.0 introduces true ACID‑compliant multi‑document transactions, bridging the gap between relational database consistency and NoSQL flexibility, while preserving high performance, scalability, and ease of development for a wide range of application scenarios.
This article introduces the fundamentals of distributed transactions, explains the ACID properties of transactions, compares local and distributed transaction architectures, and provides detailed analyses of two common distributed transaction models—X/Open XA and TCC—including their atomicity, isolation, consistency mechanisms and practical trade‑offs.
This article explains the fundamentals of database transactions, the ACID properties, and how they extend to distributed environments, covering two‑phase commit, three‑phase commit, and the TCC model while discussing their advantages, limitations, and practical examples.
This article explains the fundamentals of database transactions, the ACID properties, and how they are implemented in relational systems before exploring distributed transaction challenges and solutions such as 2PC, 3PC, TCC, and message‑based approaches.
This article explains the fundamentals of relational database transactions, the ACID properties, and various distributed transaction protocols such as 2PC, 3PC, TCC, message‑based approaches, and 1PC, while discussing their advantages, drawbacks, and practical considerations.
This article provides a clear, step‑by‑step explanation of database transactions, covering the ACID properties, how atomicity, consistency, isolation, and durability are implemented, and introduces MVCC as a modern concurrency control technique with practical examples and diagrams.
This article explains the challenges of consistency in distributed systems, introduces the CAP theorem and ACID properties, describes common distributed transaction techniques such as local message tables, transactional message middleware like RocketMQ, and details the two‑phase and three‑phase commit protocols with their advantages and drawbacks.
This article explains distributed system fundamentals—CAP theorem, ACID properties, consistency models, and how 2PC and 3PC protocols, along with message‑middleware solutions like RocketMQ, address the challenges of achieving reliable complex distributed transactions.
This article explains MySQL's transaction fundamentals, the ACID properties, common concurrency problems such as dirty reads, non‑repeatable reads and phantom reads, and demonstrates each isolation level with step‑by‑step command‑line examples and recommendations for real‑world applications.
Ensuring final data consistency in modern applications—whether enterprise or internet—requires understanding ACID, CAP, BASE theories and applying practical techniques such as single-database transactions, two-phase commit, transactional message queues, compensation tasks, async callbacks, and double-check mechanisms to build robust distributed systems.
This article examines the challenges of consistency in large‑scale distributed service systems, presents real‑world case studies such as payment transfers and order processing, and outlines practical patterns—including ACID/BASE theory, two‑phase and three‑phase commit, TCC, query, compensation, periodic reconciliation, and reliable messaging—to help engineers design robust, eventually consistent architectures.
This article examines the challenges of achieving consistency in large‑scale distributed service systems, outlines common inconsistency scenarios such as split‑brain and lost updates, and presents practical patterns—including ACID/BASE trade‑offs, two‑phase and three‑phase commit, TCC, query, compensation, and reliable messaging—to guide engineers in designing robust, eventually consistent architectures.
This article explains the fundamental ACID properties of database transactions, details the four isolation levels—READ_UNCOMMITTED, READ_COMMITTED, REPEATABLE_READ, SERIALIZABLE—illustrates common concurrency issues like dirty, non‑repeatable, and phantom reads with examples, and shows how Spring’s transaction propagation and additional features can be leveraged to manage them effectively.
This article explains the fundamentals of transactions, the ACID properties, isolation levels, distributed transactions, the CAP theorem, and the BASE model, illustrating how they shape consistency, availability, and reliability in modern database and distributed system design.
An in‑depth overview of NoSQL databases explains the limitations of traditional relational systems, details ACID properties, introduces the CAP theorem and BASE model, compares RDBMS with NoSQL, outlines advantages, disadvantages, history, classifications, and real‑world usage examples.
This article explains the four MySQL isolation levels, their effects such as dirty reads, non‑repeatable reads and phantom reads, shows how to view and change the isolation level, and reviews the ACID principles of atomicity, consistency, isolation, and durability.
This talk walks through the evolution of databases, explains the challenges of building a distributed key‑value system that provides full ACID properties, and details the architectural components, sharding, migration, snapshot isolation, two‑phase commit, timestamp handling, and distributed transaction processing techniques.
This article explains why transactions are essential, describes the ACID properties, details MySQL's isolation levels and their effects, outlines InnoDB's redo/undo logging mechanism, and introduces distributed transaction models with two‑phase commit, providing practical examples and diagrams.
This article explains the concept of database transactions, their ACID properties, and provides a step‑by‑step Node.js example using the Bookshelf.js ORM to safely perform multi‑table operations within a transaction.
This article explains the ACID fundamentals, common concurrency anomalies such as dirty, non‑repeatable and phantom reads, the four SQL‑standard isolation levels, how MySQL implements them, and step‑by‑step command‑line tests demonstrating their effects on real transactions.
PostgreSQL implements transactions through a three‑layer architecture—top, middle, and bottom—where the top layer handles user‑visible commands, the middle layer processes statement‑level actions, and the bottom layer manages low‑level atomic operations, each with specific functions and state handling.
The article revisits the CAP theorem, explains why the classic "two‑of‑three" interpretation is misleading, compares ACID, BASE and CAP, discusses the role of latency, and presents practical strategies for detecting, handling, and recovering from network partitions in distributed systems.
