Tagged articles
Saga
69 articles · Page 1 of 1
Seata 2.6.0 embeds an MCP server in its Console, letting AI clients query and manage distributed transactions via natural language with mandatory confirmation for destructive operations, covering tool categories, security design, setup steps, and real interaction examples.
AI integrationMCPModel Context Protocol
0 likes · 15 min read

This article details ten core microservices design patterns — including Database per Service, Event Sourcing, CQRS, Saga, BFF, API Gateway, Strangler, Circuit Breaker, Externalized Configuration, and Consumer-Driven Contract Testing — with pros, cons, use cases, and technology examples for each.
API GatewayCircuit BreakerSaga
0 likes · 31 min read

This article details production-ready Go distributed transaction patterns including Outbox for reliable event publishing, RocketMQ transaction messages, SAGA orchestration with compensation, TCC resource reservation, payment unknown-state handling, capacity planning, fault validation matrices, and operational recovery loops with concrete PostgreSQL schemas and Go code examples.
GoOutbox PatternPostgreSQL
0 likes · 45 min read


liandkSep 30, 2026 · Backend Development
This article provides a comprehensive guide to distributed transactions in microservices, covering CAP/BASE theory, four major patterns (2PC, local message table, TCC, SAGA), eight common production faults with root causes and fixes, selection guidelines, a troubleshooting SOP, and high-availability standards.
2PCBASE theoryCAP theorem
0 likes · 19 min read

This article shows how to replace heavyweight distributed‑transaction frameworks such as Seata with a lightweight, production‑grade SAGA orchestrator built from a Java state machine, MySQL persistence and Spring Boot, covering architecture, state‑machine design, database schema, core orchestration logic, recovery, exception handling and practical deployment tips.
IdempotencyJavaSaga
0 likes · 46 min read

The article explains how sharing the full User model inside the Order aggregate creates hidden coupling that blows up microservice performance, and shows a step‑by‑step DDD bounded‑context refactor with event‑storming, outbox, saga, idempotency and CQRS using Java 21, Spring Boot 3.x, MySQL and Kafka.
DDDJavaKafka
0 likes · 35 min read

This article explains event‑driven architecture, its advantages, core concepts such as events, producers, consumers and brokers, and demonstrates practical implementations with AWS SQS, RabbitMQ, Apache Kafka, AWS EventBridge, CloudEvents format, and the Saga pattern for reliable distributed workflows.
AWSEventBridgeKafka
0 likes · 9 min read

The article examines why ultra‑high‑throughput systems must move from costly strong consistency to eventual consistency, explaining consistency layering, the trade‑offs of coordination latency, availability, and tail latency, and how local message tables, idempotent delivery, compensation (Saga) and periodic reconciliation together ensure data eventually aligns without sacrificing performance.
ConsistencySagaTransactional Outbox
0 likes · 17 min read

This guide details implementing CQRS and Event Sourcing in Spring Boot, covering command/query separation, event bus choices (Outbox pattern, Kafka), projection idempotency, state snapshots for performance, Saga-based compensation for distributed transactions, and practical tuning tips for production workloads.
Event BusIdempotencyKafka
0 likes · 14 min read

The article explains why traditional two‑phase commit (2PC) is unsuitable for micro‑service workflows, introduces the Saga pattern as a series of local transactions with compensations, compares orchestration‑based and choreography‑based implementations, and provides concrete design guidelines, code samples, and state‑machine persistence strategies.
ChoreographySagacompensation
0 likes · 18 min read

The article explains why a single order operation can involve multiple services and databases, introduces the challenges of distributed transactions, and compares three common solutions—Two‑Phase Commit, TCC, and Saga—detailing their mechanisms, strengths, weaknesses, and suitable scenarios.
2PCConsistencySaga
0 likes · 12 min read

The article explains why ACID guarantees break down in distributed systems, introduces the BASE and CAP trade‑offs, then details six concrete transaction solutions—2PC, 3PC, TCC, Saga, local message tables, and reliable messages—highlighting their processes, drawbacks, and a decision framework for selecting the right approach.
2PC3PCACID
0 likes · 19 min read

The article compares Seata‑AT, TCC, and Saga distributed‑transaction patterns, explains their two‑phase or three‑phase mechanisms, outlines performance and consistency trade‑offs, and provides concrete guidance on which solution fits backend micro‑service scenarios such as core commerce, third‑party integration, or admin tools.
AT modeSagaSeata
0 likes · 8 min read

The article outlines a step‑by‑step architecture redesign for a 20‑year‑old monolithic production system, detailing problem analysis, a phased microservice migration using the "killer" pattern, data‑sync strategies, distributed transaction handling, observability, rollback mechanisms, and practical interview‑style insights.
CanalDDDData Consistency
0 likes · 15 min read

The article reviews the most common distributed transaction patterns—TCC, Saga, reliable messaging, 2PC, and Seata's AT mode—explaining their principles, ideal use‑cases, implementation details, and trade‑offs so architects can select the most suitable solution for their microservice systems.
2PCReliable MessagingSaga
0 likes · 15 min read

This article explains why distributed transactions are essential in microservice architectures, introduces Alibaba's open‑source Seata solution, compares its AT, TCC and Saga modes, shows step‑by‑step Docker deployment, provides full Spring Cloud code examples, and lists common pitfalls and debugging tips.
AT modeDocker ComposeMySQL
0 likes · 12 min read

Distributed transactions have no universal silver bullet; architects must balance consistency, latency, throughput, complexity, and operational cost, and choose among SAGA, TCC, and Outbox patterns based on concrete trade‑offs, failure handling, and real‑world engineering constraints.
JavaOutboxSaga
0 likes · 47 min read

This article demonstrates how to design and implement a miniature yet fully functional industrial intelligent scheduling system in Go, leveraging a workflow engine, priority queue, saga‑based transactions with FSM state management, concurrent station execution, and write‑ahead logging for reliable, real‑time factory automation.
ConcurrencyFSMGo
0 likes · 9 min read

This guide explains Seata's open‑source distributed transaction solution, compares its AT, TCC, Saga, and XA modes, details core components and workflow, and provides step‑by‑step instructions for quick integration in microservice backends.
AT modeSagaSeata
0 likes · 7 min read

The article explains why distributed transactions are inevitable in microservice architectures, outlines the challenges of data consistency, fault handling, and performance, and presents practical solutions such as message‑queue eventual consistency, two‑phase commit, Saga patterns, and tooling like Spring Cloud, Atomikos, and Narayana.
2PCMessage QueueSaga
0 likes · 17 min read

This article analyzes common distributed‑transaction scenarios, explains the CAP theorem’s relevance, compares ACID/BASE, TCC, XA, 2PC/3PC, Saga and AT patterns, and provides a decision‑making framework to help architects select the most suitable approach for their microservice systems.
CAP theoremSagaTCC
0 likes · 18 min read

This article introduces eight essential distributed‑transaction techniques—including 2PC, 3PC, TCC, Saga, distributed locks, local message tables, reliable message transactions, and best‑effort notifications—detailing their workflows, advantages, drawbacks, and suitable business scenarios to help engineers choose the right solution.
2PC3PCConsistency
0 likes · 16 min read

The article explains the challenges of distributed transactions in microservices, introduces the Saga pattern as a solution, compares choreography and orchestration implementations, and outlines their benefits, drawbacks, and rollback mechanisms using an e‑commerce order processing example.
ChoreographySagadistributed transactions
0 likes · 7 min read

This article shares practical experiences and detailed technical solutions for applying Domain‑Driven Design, Clean (Onion) Architecture, CQRS, and Saga patterns in backend systems, covering theory recap, modeling methods, module separation, code examples, and distributed transaction strategies.
BackendDDDSaga
0 likes · 28 min read

This article explains the fundamentals of database transactions, the ACID properties, and why distributed transactions are needed, then walks through the implementation details of redo/undo logs, local transactions, CAP and BASE theory, and evaluates five major distributed‑transaction solutions—2PC, TCC, local‑message tables, maximum‑effort notification, and Saga—with concrete examples, pros, and cons.
2PCACIDBASE
0 likes · 20 min read

The article details Shopee’s seadt‑SAGA framework—a Go‑based distributed transaction solution that implements the SAGA pattern via two modes, orchestration with a central coordinator and collaboration with embedded logic, explains their state‑machine designs, compares rollback ordering using vector clocks versus sequence numbers, and discusses each mode’s trade‑offs.
CollaborationGoSaga
0 likes · 23 min read

This guide introduces Seata Saga’s distributed transaction model, explains its advantages and drawbacks, walks through deployment, JSON state‑machine design, unit‑test exploration, and best‑practice recommendations for reliable microservice orchestration, including compensation strategies, isolation handling, and performance tuning tips.
BackendSagaSeata
0 likes · 13 min read

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.
BackendDTMSaga
0 likes · 15 min read


ITPUBMay 1, 2023 · Backend Development
This article demystifies distributed transactions using Alibaba's Seata, explaining reverse compensation, core concepts (TC, TM, RM), the two‑phase commit protocol, and detailed walkthroughs of AT, TCC, XA, and Saga modes with code examples and step‑by‑step procedures.
AT modeSagaSeata
0 likes · 14 min read

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.
2PCA*Saga
0 likes · 24 min read

The article explains how the Saga pattern—using either choreography or orchestration—enables reliable distributed transactions across microservices by coordinating local ACID operations, handling compensating actions, and addressing the challenges of consistency, rollback, and scalability.
ChoreographySagadistributed transactions
0 likes · 9 min read


ITPUBNov 17, 2022 · Backend Development
This article explains the fundamentals of ACID, compares monolithic and distributed transaction models, and details various distributed transaction strategies—including 2PC, 3PC, TCC, local message tables, MQ transactions, max‑effort notifications, Saga, and Seata—highlighting their mechanisms, trade‑offs, and practical considerations.
2PC3PCSaga
0 likes · 20 min read

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.
AT modeSagaSeata
0 likes · 14 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


JavaEdgeDec 21, 2021 · Backend Development
This article explains the fundamentals of transactions, compares monolithic and distributed transaction models, and walks through various distributed transaction solutions such as 2PC, 3PC, TCC, local message tables, MQ transactions, max‑effort notifications, Saga, and Seata, highlighting their trade‑offs and practical considerations.
2PC3PCSaga
0 likes · 20 min read

This article explains how data consistency is achieved through local ACID transactions, global XA/2PC mechanisms, CAP and BASE theories, and practical patterns such as reliable events, TCC, and SAGA, providing a comprehensive overview for architects designing distributed systems.
ACIDCAP theoremConsistency
0 likes · 22 min read

This article traces Seata’s development from its 2014 origins as Alibaba’s TXC middleware, through its 2016 cloud service launch and 2019 open‑source release, detailing its architecture, module composition, core roles, and the four transaction modes (AT, TCC, Saga, XA) with practical comparisons.
AT modeSagaSeata
0 likes · 17 min read

This article explains the fundamentals of database transactions, defines distributed transactions, and provides a comprehensive comparison of classic solutions such as XA, SAGA, TCC, local message tables, transaction messages, maximum‑effort notifications, and AT mode, while also covering exception handling and the sub‑transaction barrier technique.
BackendSagaTCC
0 likes · 19 min read

The article reviews the most frequent errors encountered while adopting microservice architecture—excessive customization, uncontrolled complexity, and vague definitions—illustrating each with real‑world experiences, a saga implementation using Redis streams and Go, and practical advice to avoid similar pitfalls.
GoRedisSaga
0 likes · 6 min read

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.
BackendSagaTCC
0 likes · 15 min read

This article explains the fundamentals of distributed transactions, compares classic solutions such as XA, Saga, TCC, local message tables, and transaction messages, and presents a sub‑transaction barrier technique that gracefully handles idempotency, empty rollbacks, and hanging issues in microservice architectures.
DTMSagaTCC
0 likes · 24 min read

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.
BackendSagaTCC
0 likes · 19 min read

This article introduces the fundamental concepts of distributed transactions, explains ACID and BASE properties, and systematically presents classic solutions such as two‑phase commit, SAGA, TCC, local message tables, transaction messages, maximum‑effort notifications, and sub‑transaction barriers for reliable microservice architectures.
SagaTCCTwo-Phase Commit
0 likes · 16 min read

The article explains the concept of distributed transactions, why they are needed in micro‑service architectures, presents the CAP and BASE theories, and reviews major solutions such as two‑phase commit, three‑phase commit, TCC, local message tables, message‑based transactions, max‑effort notifications, Sagas and the Seata framework.
2PC3PCCAP theorem
0 likes · 15 min read


21CTOJul 9, 2021 · Backend Development
This article reviews essential microservice design patterns—including Database per Service, Event Sourcing, CQRS, Saga, Backend‑for‑Frontend, API Gateway, Strangler, Circuit Breaker, Externalized Configuration, and Consumer‑Driven Contract Testing—explaining their advantages, drawbacks, when to apply them, and common technology implementations.
API GatewaySagacqrs
0 likes · 28 min read

The article explains why traditional two‑phase commit fails in microservice architectures, introduces the Saga pattern as a solution, compares choreography and orchestration implementations, illustrates a step‑by‑step e‑commerce example, and discusses rollback handling, benefits, and drawbacks.
ChoreographySagabackend architecture
0 likes · 7 min read

This article explains key microservice design patterns—including Database per Service, Event Sourcing, CQRS, BFF, API Gateway, Strangler, Circuit Breaker, Externalized Configuration, and Consumer‑Driven Contract Testing—detailing their advantages, disadvantages, suitable scenarios, and example technologies for building scalable, resilient backend systems.
Sagabackend architecturecqrs
0 likes · 26 min read


ByteFEMay 18, 2021 · Frontend Development
This article explains what Dva is, the problems it solves, its advantages and disadvantages, core concepts, minimal application structure with code examples, and the underlying implementation details, comparing it with React, React‑Redux, and Redux‑Saga, helping developers understand its role in frontend development.
DVAReduxSaga
0 likes · 17 min read

This article explains the importance of distributed transactions in micro‑service architectures, reviews ACID properties, compares various solutions such as 2PC/3PC, XA, local message tables, transactional messages, TCC, Saga, and introduces the Seata framework with its AT, TCC, and Saga modes, while also discussing consistency versus consensus with Paxos.
2PCConsistencySaga
0 likes · 14 min read

This article explores the fundamentals of distributed transactions in microservice architectures, detailing ACID properties, classic protocols like 2PC/3PC and XA, modern patterns such as TCC, Saga, local message tables, transaction messages, and the Seata framework, while comparing their trade‑offs with Paxos consensus.
2PCConsistencySaga
0 likes · 16 min read

This article outlines the background, design choices, and implementation details of a data‑consistency engine for an advertising billing platform, comparing TCC and saga‑style approaches, describing the state‑machine architecture, configuration, initialization, and asynchronous execution patterns.
BackendData ConsistencySaga
0 likes · 9 min read

This article explains the challenges of distributed transactions in micro‑service architectures and reviews major solutions such as 2PC/3PC, XA, TCC, Saga, local message tables, transactional messages, and the Seata framework, comparing their consistency, performance, and implementation trade‑offs.
2PCSagaSeata
0 likes · 18 min read

This article explains the challenges of cross‑service communication in microservice architectures and presents a comprehensive set of design patterns—including synchronous and asynchronous messaging, event‑driven approaches, saga, event sourcing, CQRS, outbox, CDC, idempotency, eventual consistency, distributed tracing, and service mesh—to help engineers build reliable, scalable distributed systems.
Sagacommunicationcqrs
0 likes · 17 min read

This article explains why data consistency is critical in microservice architectures, introduces the Saga pattern and its execution and recovery mechanisms, compares it with two‑phase commit and TCC, and presents a centralized Saga design using ServiceComb for reliable distributed transactions.
2PCData ConsistencySaga
0 likes · 18 min read

Seata is an open‑source Java framework that simplifies distributed transactions by offering a Transaction Coordinator, embedded Transaction and Resource Managers, and four modes—AT, TCC, Saga, and XA—each with distinct consistency and performance trade‑offs, enabling high‑concurrency, zero‑intrusion handling of multi‑node operations.
AT modeJavaSaga
0 likes · 15 min read

This article explains the concept and implementation approaches of SAGA as a distributed transaction solution, covering the problem definition, the two strategies—Choreography and Orchestration—including their workflows, event handling, state machine coordination, advantages, drawbacks, and references to Alibaba's Seata framework.
ChoreographySagaSeata
0 likes · 7 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

The article, the second in a DDD practice series, shows how immutable domain events can capture business milestones and be stored and published, introduces Saga—both choreography and orchestration—to manage distributed transactions with compensations, and explains how CQRS separates read and write models, illustrating each concept with Java code while highlighting the resulting decoupling, scalability, and modeling clarity alongside added complexity and storage challenges.
JavaSagacqrs
0 likes · 21 min read

This article walks through setting up Seata for distributed transaction management in a Spring Cloud microservices project, covering concepts of AT, TCC, and Saga modes, configuration of Seata server and clients, code examples for transaction handling, and a practical e‑commerce demo.
AT modeSagaSeata
0 likes · 20 min read


AntTechJul 29, 2019 · Backend Development
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.
AT modeSagaSeata
0 likes · 15 min read

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.
SagaShardingSphereXA
0 likes · 18 min read

This article introduces a series of microservice design patterns—including database isolation, observability, and cross‑cutting concerns—explaining the underlying problems each pattern solves and providing concrete solutions such as CQRS, Saga, log aggregation, health checks, and blue‑green deployments.
Circuit BreakerSagabackend architecture
0 likes · 13 min read

This article explains the challenges of distributed transactions in microservice architectures, covering database transaction fundamentals, the CAP and BASE theories, and evaluates various solutions such as 2PC, TCC, local message tables, MQ transactional messages, Sagas, and introduces the open‑source .NET CAP framework.
2PCBackendCAP theorem
0 likes · 15 min read

This article explains the fundamentals of database transactions, the ACID properties, and how they are implemented, then delves into distributed transaction challenges and solutions such as two‑phase and three‑phase commit, XA, Saga patterns, choreography vs. orchestration, and message‑based transaction mechanisms.
2PC3PCACID
0 likes · 16 min read


21CTOAug 23, 2018 · Databases
This article explains the fundamentals of database transactions, the ACID properties, and how they are implemented, then delves into distributed transaction challenges and solutions such as two‑phase commit, three‑phase commit, XA, and Saga patterns, highlighting their trade‑offs and practical usage.
2PCACIDMySQL
0 likes · 19 min read

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.
2PCACIDSaga
0 likes · 17 min read

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.
2PCACIDCAP
0 likes · 17 min read

This article explains the challenges of preserving ACID properties in distributed environments, introduces CAP and BASE trade‑offs, reviews industry transaction models such as XA, 2PC, weak XA, BED, TCC and Saga, and details how ShardingSphere implements and plans to evolve support for these distributed transaction mechanisms.
BASECAPSaga
0 likes · 19 min read

The article summarizes four technical sessions from QCon covering Alibaba's Pandora microservice isolation framework and its boot solution, 51 Credit Card's monitoring platform design, JD's Akimed service platform with ContainerMesh and capability mapping, and a saga‑based distributed transaction library, highlighting challenges, implementations, and practical insights.
BackendPandoraSaga
0 likes · 11 min read
