0 views collected around this technical thread.
This article explores strategies for seamless data migration—including full, incremental, and binlog‑based approaches—and examines distributed transaction models such as XA, BASE, TCC, and AT, outlining their components, workflows, advantages, challenges, and supporting tools like Seata and Canal.
This article analyzes the challenges of distributed transactions in a micro‑service order system, compares XA, TCC, and SAGA patterns, and details how the open‑source DTM framework is applied to achieve reliable order creation while handling crashes, rollbacks, idempotency, and network anomalies.
This article explains the challenges of distributed transactions in micro‑service architectures and presents Seata's various solutions—including two‑phase commit, XA, AT, TCC, Saga and message‑based approaches—while covering fundamental concepts such as ACID, CAP and BASE.
This article introduces Seata's approach to distributed transactions, covering the concept of reverse compensation, core components (TC, TM, RM), the two‑phase commit protocol, and detailed walkthroughs of Seata's AT, TCC, XA, and Saga modes with practical examples and diagrams.
This article explains the XA specification, demonstrates MySQL XA commands, and shows how Sharding-JDBC integrates XA transactions using Atomikos, including required dependencies, configuration, annotations, and testing steps, while also providing practical code examples and deployment tips.
This article explains the fundamentals of distributed transactions, compares classic solutions such as two‑phase commit (XA), SAGA, TCC, local message tables, transaction messages, and maximum‑effort notifications, and presents a sub‑transaction barrier technique to handle network anomalies and ensure idempotency, isolation, and rollback safety.
This article explains the fundamentals of distributed transactions, illustrates classic solutions such as two‑phase commit (XA), SAGA, TCC, local message tables, transactional messaging, and maximum‑effort notifications, and introduces a sub‑transaction barrier technique to handle network anomalies in microservice architectures.
This article explains the principles, advantages, and drawbacks of various distributed transaction solutions—including XA two‑phase commit, three‑phase commit, TCC, Saga, and message‑based eventual consistency—while showing how they are implemented in Java/Spring environments and when each should be used.
This article explains the principles, workflows, advantages and drawbacks of various distributed transaction solutions—including XA two‑phase commit, Java Transaction API, chained transaction managers, three‑phase commit, TCC, reliable message‑based eventual consistency and maximum‑effort notification—while comparing ACID and BASE theories for modern backend systems.
This article introduces five common distributed transaction patterns—XA two‑phase commit, TCC, local message table, reliable message eventual consistency, and max‑effort notification—explains their principles, advantages, drawbacks, and provides interview questions and suggested answers for each.
This article provides a comprehensive technical overview of Seata's newly introduced XA transaction mode, explaining the XA protocol, its advantages over compensation‑based modes, the design and implementation details within Seata, and practical usage guidelines for developers.
This article explains how Ant Financial tackled cross‑service and cross‑database data‑consistency challenges caused by horizontal sharding and service‑oriented decomposition, introduces its home‑grown distributed‑transaction middleware and the open‑source Seata project with AT, TCC, Saga and XA modes, and shares performance‑optimisation and high‑availability practices.
This article provides a comprehensive analysis of DBLE's XA transaction implementation, covering XA protocol basics, DBLE's architecture, code structure, execution flow, error handling, transaction logging, recovery mechanisms, and practical considerations for distributed transactions in database middleware.
Apache ShardingSphere provides an integrated distributed transaction solution combining traditional ACID‑compliant two‑phase commit, flexible Saga‑based transactions, and automatic transaction management, detailing their architectures, features, trade‑offs, and usage guidelines for developers handling multi‑database microservice environments.